chore: back-merge main into dev (sync after PR #6) - #7
Merged
Conversation
chore: activate auto-release pipeline on main (sync dev → main, no version bump)
PR #6 merged dev into main to activate the auto-release pipeline. Back-merge main into dev so dev's history includes the release merge commit. No file changes — trees are identical. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Summary
Git-flow back-merge after #6 activated the auto-release pipeline on
main.#6 merged
dev → main(a merge commit now lives only onmain). This bringsthat merge commit back into
devso the histories stay reconciled. No filechanges — the trees are already identical.
Type of change
Checklist
git diff origin/devis empty)deva superset ofmainfor the next release merge