ci: mark major dependabot bumps as breaking and run CI on merge groups - #1958
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Member
Author
|
🎉 This PR is included in version 21.1.11 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
automerge.yml: usedependabot/fetch-metadatato inspect the semver level of each dependabot update instead of hand-parsing swipl-wasm versions out ofpackage.json.BREAKING CHANGE:footer to the PR body, so the squash commit triggers a semantic-release major. Previously a major bump such as swipl-wasm 7 -> 8 (fix!: bump swipl-wasm from 7.0.10 to 8.0.1 #1945) kept itsfix:title and would ship as a patch; the oldgh pr merge --subject "BREAKING CHANGE: ..."approach also put the note in the squash subject, which the angular commit parser cannot read (verified: it yields no release), and--subject/--bodyflags are ignored by merge queues anyway.feat:mapping (now via a PR retitle); patch bumps, dev-dependency bumps and github-actions bumps keep their currentfix:/chore:behaviour.pull_request_target; the new flow does not check out any code.nodejs.yml,codeql-analysis.yml: addmerge_group:triggers so all required checks also run for merge-queue entries.Why
semantic-release's default (angular) commit-analyzer treats a commit as a major only when a line of the commit body starts with
BREAKING CHANGE:. It does not understand thetype!:shorthand — verified against@semantic-release/commit-analyzer@13.0.1as pinned in the lockfile, wherefix!: ...produces no release at all.Repository squash settings were switched to
squash_merge_commit_title=PR_TITLE/squash_merge_commit_message=PR_BODY, so the PR title and body deterministically become the squash commit message (previously a single-commit PR used the commit's own message, ignoring PR title edits). This is what both the reworked automerge flow and the merge queue rely on.🤖 Generated with Claude Code