Confluence api v2 and deprecated functions

[davideicardi]

Now that many API are marked as deprecated on both confluence and library side, due to the introduction of v2 rest API, what is the suggested way to replace them?

Can we implement them on this library?
Do you need help?

[MrRefactoring]

Addressed by #151 — confluence.js 3.0, open now.

v2 is fully covered (30 namespaces) and ships alongside v1 in a single package, driven by one host. The way off the deprecated v1 operations is their v2 equivalent: the migration guide in that PR maps each removed v1 operation to its v2 replacement, one-to-one.

Thanks for the offer to help — review on the PR is very welcome.

[MrRefactoring]

Shipped: confluence.js 3.0.0 is on npm.

To close the loop on the original question — how to replace the deprecated v1 operations — the answer is their v2 equivalents, and they are all here now. MIGRATION.md maps each of the 37 v1 operations Atlassian has dropped since 2.x to its v2 replacement, one-to-one, and a codemod covers the mechanical rewrites.

Worth being precise about one thing: v1 is not going away here. Atlassian has not deprecated the v1 API itself, and v1 and v2 cover different ground, so 3.0 ships both as peers from a single package rather than treating v2 as a migration target you must reach.

Also in this release: fetch instead of axios, zod as the only runtime dependency, every response validated against a schema, a typed error per failure mode, and one build that works in Node and the browser.

• Release notes: https://github.com/MrRefactoring/confluence.js/releases/tag/v3.0.0
• Docs: https://mrrefactoring.github.io/confluence.js

Thanks for the nudge and for the offer to help — it is what moved this along.