Skip to content

ci: drop @semantic-release/git so releases work under branch protection#3

Merged
MegaManSec merged 2 commits into
mainfrom
drop-git-plugin-from-release
May 28, 2026
Merged

ci: drop @semantic-release/git so releases work under branch protection#3
MegaManSec merged 2 commits into
mainfrom
drop-git-plugin-from-release

Conversation

@MegaManSec
Copy link
Copy Markdown
Owner

No description provided.

The git plugin pushes a `chore(release): X.Y.Z [skip ci]` commit back to
`main`, which fails when the branch is protected. Tags and GitHub
Releases are still created by `@semantic-release/github` via the API,
which is not subject to branch-push protection.

Trade-offs:
- CHANGELOG.md is no longer maintained in the repo (release notes still
  live on each GitHub Release page).
- MARKETING_VERSION in the pbxproj stays static. The build pipeline
  rewrites it via sed before xcodebuild, so the shipped .app has the
  correct version regardless.

Also dropped:
- @semantic-release/changelog (would write CHANGELOG.md that never
  gets persisted) from both npm install steps.
- The release job's `cp artifacts/project.pbxproj` step, which only
  existed so the git plugin had the version-bumped pbxproj to commit.
Since @semantic-release/git was removed, nothing regenerates CHANGELOG.md
on each release. Release notes still live on the GitHub Releases page;
keeping the file in-tree would just leave a permanently stale snapshot.
@MegaManSec MegaManSec merged commit d5c03b6 into main May 28, 2026
1 check passed
@github-actions
Copy link
Copy Markdown

🎉 This PR is included in version 2.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@MegaManSec MegaManSec deleted the drop-git-plugin-from-release branch May 28, 2026 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant