Skip to content

ci: open pull requests against master only - #54

Merged
LESANF merged 6 commits into
masterfrom
0.0.9
Sep 21, 2026
Merged

LESANF merged 6 commits into
masterfrom
0.0.9

Conversation

@LESANF

@LESANF LESANF commented Sep 21, 2026

Copy link
Copy Markdown
Owner

Pull requests now target master only. Features reach the version branch by local merge, CI runs on version-branch pushes, and a PR whose base is not master fails.

A release is the tag, not the master merge. The CLI pins the template by tag, so master may run ahead without reaching users.

No version bump. Nothing changes for consumers.

🤖 Generated with Claude Code

LESANF and others added 6 commits September 17, 2026 13:21
…test

The packument at registry.npmjs.org is served through a CDN that kept
returning the previous dist-tag for several minutes after a publish had
landed, so the script reported a missing publish that had already
happened. Send Cache-Control: no-cache and a cache-busting query.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
fix(release-check): bypass the registry CDN cache when reading npm latest
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
docs: bring the progress log's release state up to 0.0.9
GitHub attributes a commit to the first pull request that carried it, so
commits merged into a version branch by PR never counted for the later
master PR, which only added a merge commit. Features now reach the version
branch by local merge, CI runs on version-branch pushes, and a PR whose
base is not master fails. A release is the tag, not the master merge: the
CLI pins the template by tag, so master may run ahead of it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@LESANF
LESANF merged commit eddfc42 into master Sep 21, 2026
2 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