Skip to content

release.sh: drop [skip ci] from version bump; allow manual tag_on_main#686

Open
bjorkert wants to merge 1 commit into
devfrom
release-skip-ci-fix
Open

release.sh: drop [skip ci] from version bump; allow manual tag_on_main#686
bjorkert wants to merge 1 commit into
devfrom
release-skip-ci-fix

Conversation

@bjorkert

Copy link
Copy Markdown
Member

The [skip ci] on the release version-bump commit had two harmful side effects observed during the v6.2.0 release:

  • It skipped the required SwiftFormat lint check, leaving the release PRs stuck at BLOCKED (requiring a manual override to merge).
  • It skipped tag_on_main.yml, so the v6.2.0 tag was never created automatically and had to be pushed by hand.

The [skip ci] was only there to stop auto_version_dev from re-bumping when the commit lands on dev — but that workflow already prevents this via its own "Skip if Config.xcconfig was changed in this push" guard. So the token is redundant for its intended purpose and is removed.

Also adds a workflow_dispatch trigger to tag_on_main.yml as a safety net: if a tagging run is ever skipped, the tag can be created by dispatching the workflow against main (idempotent — it skips if the tag already exists).

Note: once this is merged, the SwiftFormat requirement can safely be enabled for main (Phase 3) without blocking future release PRs.

The [skip ci] on the version-bump commit skipped the required SwiftFormat lint check (blocking the release PRs) and the tag_on_main workflow (no auto-tag). Remove it; auto_version_dev already prevents re-bumping via its Config.xcconfig guard. Also add a workflow_dispatch trigger to tag_on_main so the tag can be created manually if a run is ever skipped.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant