Skip to content

release v0.21.1 - #340

Merged
dave-doty merged 7 commits into
mainfrom
dev
Aug 1, 2026
Merged

release v0.21.1#340
dave-doty merged 7 commits into
mainfrom
dev

Conversation

@dave-doty

Copy link
Copy Markdown
Member

Deploys the dev-branch automation to main.

The functional point of this release is retarget-pr-to-dev.yml: pull_request_target reads its workflow file from the default branch, so that workflow cannot run until it exists on main. This release also removes the deleted reopen-dev-closes.yml from main.

No change to the package itself — everything since v0.21.0 is CI, tooling and documentation.

dave-doty and others added 7 commits August 1, 2026 11:23
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.
@dave-doty
dave-doty merged commit b2d09d5 into main Aug 1, 2026
8 checks passed
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