Conversation
back-merge main into dev after v0.21.0
Every push to main is a release, so a dependabot PR merged into main without a version bump would fail the release workflow. target-branch sends them to dev, where they ride along with the next release like every other change.
…target-dev point dependabot PRs at dev instead of main
…again main is the default branch, which keeps GitHub's "fixes #123" auto-closing tied to releases and keeps the repository page and release PRs pointed at main. The cost was having to remember to base branches and PRs on dev; these changes automate that instead. branch-for-issue.ps1 / branch-for-issue.sh wrap `gh issue develop`: given an issue number they create a branch named from the issue, based on dev, linked to the issue, and check it out. The "Create a branch" link on the issue page cannot do this -- it always bases the branch on the default branch, with no way to choose dev, and GitHub Desktop has no issue-aware equivalent. retarget-pr-to-dev.yml switches any newly opened pull request from main to dev and explains in a comment, so contributors never need to know the convention. The release PR is exempt, recognized as a dev head branch IN THIS REPOSITORY: a fork's branch may also be named dev, and those are ordinary contributions. label-fixed-in-dev.yml replaces reopen-dev-closes.yml, which is deleted. That one was needed only while dev was the default branch: GitHub closed such issues immediately and a bot had to reopen them, producing a close/reopen notification pair for every fix. Now nothing closes them, so the label is simply added to an issue that stays open -- same result, no notification noise. release.yml's close-issues job now comments on issues that are already closed. With main as the default branch GitHub closes them natively seconds before the job runs, which would otherwise silently drop the "Released in vX.Y.Z" note. The comment is skipped if one for this version is already present, so re-running the workflow does not duplicate it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…v-branch-workflow automate the dev-branch workflow now that main is the default branch again
No functional change to the package: everything since v0.21.0 is CI, tooling and documentation. The bump exists because every push to main is a release, and this release deploys retarget-pr-to-dev.yml to main, where pull_request_target reads its workflow file from -- without which that workflow cannot run.
…n-0.21.1 bump version to 0.21.1
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.
Deploys the dev-branch automation to
main.The functional point of this release is
retarget-pr-to-dev.yml:pull_request_targetreads its workflow file from the default branch, so that workflow cannot run until it exists onmain. This release also removes the deletedreopen-dev-closes.ymlfrommain.No change to the package itself — everything since v0.21.0 is CI, tooling and documentation.