Uh oh!
There was an error while loading. Please reload this page.
ci: test every pull request, publish every merged version - #67
Draft
fiddur wants to merge 2 commits into
Draft
Conversation
test.yml builds and runs the whole suite on pull requests and develop pushes. release.yml publishes @naturalcycles/diffity with provenance when a merge lands a version npm does not have, tags it and cuts a GitHub release — and fails loudly when the version is already published but the merge changed shipped code, which is the parallel-branch gap AGENTS.md could only warn about. The bump rule is now the enforced one: every PR touching packages/*/src, packages/skills or skills bumps. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018PkYQzbsnMihHesafWvXKs
… job A quoted 'packages/*/src' pathspec matches nothing — git fnmatches wildcards against the whole path — so the enforcement wire was inert; :(glob)packages/** now provably fires on real commits. The guarded set is everything the artifact is built from, tests excluded, and AGENTS.md states the same set. Tagging is idempotent and the re-bump error names the manual recovery for a publish that failed at the tag. test.yml runs the engines floor and the release version, with read-only permissions; the concurrency comment says what the group actually gives. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018PkYQzbsnMihHesafWvXKs
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 freeto 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.
Closes#60.
Two workflows:
npm ci, build (typecheck resolves workspace imports through built dists),npm test(typecheck for all six packages, tests included, + every suite).npm ci, build, test,npm publish -w @naturalcycles/diffity --provenance --access public, tagv<version>, GitHub release with generated notes. Already published and the merge touchedpackages/*/src,packages/skillsorskills→ fail with instructions to re-bump — the parallel-branch double-bump gap AGENTS.md could until now only warn about. Already published and nothing shipped changed → quiet no-op.AGENTS.md updated to the enforced rule: bump in every PR touching those paths (a comment-only source change trips the same wire; a patch number costs nothing).
No version bump (nothing under the enforced paths). On this PR's own merge, release.yml will find 0.10.0 unpublished and perform the first publish — that needs the
NPM_TOKENsecret (automation token with publish rights on the@naturalcyclesscope) configured on the repo; without it the workflow fails visibly and can be re-run after the secret is added.Verified: YAML parses; the decide-step logic (pathspec globbing,
npm viewon the unpublished version) exercised locally against this checkout.🤖 Generated with Claude Code
https://claude.ai/code/session_018PkYQzbsnMihHesafWvXKs