chore(release): 8.3.10 — restore version sync and stop Bump version tag races

Merged
RI
3mo ago
+51-5

What

  • Restores the lost chore(release): 8.3.10 version bump onto plus, so the workspace package.json files, lerna.json and the changelogs match the 8.3.10 that is already tagged and published on npm.
  • Adds a concurrency group to .github/workflows/bump_version.yml so only one "Bump version" run executes at a time per ref.

Why

The release pipeline is currently wedged and will fail on every future push to plus.

bump_version.yml triggers on each push to plus with no concurrency guard. Merging the upstream-sync backlog produced several pushes in quick succession, so multiple runs started together, each computed the same next patch version, and each tried to create the same tag. One won; the rest died on:

fatal: tag '8.3.10' already exists
Process completed with exit code 128

The run that won pushed the tag but lost the race on the branch push, so 8.3.10 exists as a tag (commit d260116), as a GitHub release, and on npm as latest — but its version-bump commit never landed on plus. plus is still at 8.3.9.

That leaves the pipeline stuck: every subsequent run computes 8.3.9 → 8.3.10 again and dies on the existing tag. No further release can go out until the branch is moved past 8.3.10.

How

  • Cherry-picked commit d260116 (git cherry-pick -x), preserving the original github-actions[bot] authorship. Its parent was 9cad499 (chore(release): 8.3.9), already an ancestor of plus, and nothing merged since touched the version files, so it applied cleanly.
  • Added to bump_version.yml:
concurrency:
  group: bump-version-${{ github.ref }}
  cancel-in-progress: false

Runs now queue instead of racing. cancel-in-progress: false is deliberate: a bump that has already tagged should be allowed to finish pushing.

The PR title starts with chore(release):, which matches the existing skip condition in bump_version.yml, so merging this will not kick off another release.

Testing

  • bun run eslint and bun run prettier --check pass locally on the branch.
  • Verified 8.3.10 is genuinely published: registry.npmjs.org/@capacitor-plus/core reports dist-tags.latest = 8.3.10, so bumping plus to match is a correction rather than a version skip.
  • Verified git merge-base --is-ancestor d260116 origin/plus returns false, confirming the commit really is missing from the branch.
  • CI (setup / lint / test-cli / test-core / test-ios / test-android) runs on this PR.

Not Tested

  • The concurrency guard cannot be exercised until two pushes land close together again; it is a config change validated by reading, not by running.
  • No npm publish was performed or verified from this branch.

Opened by an AI agent (Cursor) while working through the upstream-sync PR backlog.

Open in Web Open in Cursor 

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Summary by CodeRabbit

  • Release

    • Released version 8.3.10 across the Capacitor, Android, iOS, core, and CLI packages.
    • This is a version-only release with no functional changes.
  • Documentation

    • Added release notes and changelog entries for version 8.3.10 across supported packages.
  • Chores

    • Improved version-release workflow handling so queued version updates can proceed reliably.