chore: resync version to the published 0.62.0

[Deborah-Digges]

Summary

main says 0.62.0 now, matching what is already on npm. This unblocks publishing — no spec, policy, or dist change.

The publish workflow bumps the version itself (npm version minor --no-git-tag-version), publishes, then commits the bump back to main. On 2026-08-11, run 31499058733 (#99) bumped 0.61.0 → 0.62.0 and published 0.62.0 to npm successfully, then failed on the Commit version bump step:

! [rejected]  main -> main (fetch first)

#100 merged mid-run, so the push lost the race. The bump commit never landed and there is no v0.62.0 tag or release, leaving main at 0.61.0 while npm serves 0.62.0. Every publish run since bumps 0.61.0 → 0.62.0 and dies:

npm error You cannot publish over the previously published versions: 0.62.0.

That is every run from #99 through #112 — 8+ consecutive failures over ~13 days. Nothing on main after #99's content has been published.

Test plan

• package.json and package-lock.json (both the top-level and packages."" entries) read 0.62.0, matching npm view @workos/openapi-spec version.
• Merging this does not trigger release.yml: package.json / package-lock.json are deliberately excluded from its paths filter to avoid a publish loop, so no run should start on merge.
• After merge, trigger release.yml via workflow_dispatch with bump: minor → publishes 0.63.0, carrying everything merged since Update OpenAPI spec (750e8f9) #99.

Follow-ups (not in this PR)

• Tag v0.62.0 at Update OpenAPI spec (750e8f9) #99's merge commit so the npm release has a matching tag and GitHub release.
• Harden the publish job against the race that caused this: the git push has no rebase or retry, so any two merges landing close together reproduce it. Either git pull --rebase origin main before pushing, or move the bump commit ahead of npm publish so a lost race fails before publishing rather than after.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

Resynchronizes the repository package version with the already-published npm version so the release workflow can advance normally.

• Updates package.json from 0.61.0 to 0.62.0.
• Updates both corresponding version fields in package-lock.json.
• Makes no specification, policy, distribution, or workflow changes.

Confidence Score: 5/5

The PR appears safe to merge because it consistently resynchronizes all package-version metadata without changing runtime or specification behavior.

The checked-in package and lockfile versions are aligned, the release workflow consumes package.json as expected, and package-only changes do not trigger the publish workflow.

Important Files Changed

Filename	Overview
package.json	Updates the package version to the already-published 0.62.0 release; no issue identified.
package-lock.json	Keeps the root and package-entry versions synchronized with package.json; no issue identified.

_{Reviews (1): Last reviewed commit: "chore: resync version to the published 0..." | Re-trigger Greptile}