Repository navigation
Prepares the 0.6.1 release - #213
Merged
Merged
Conversation
A patch, and a documentation release: 0.6.1 carries 0.6.0's code unchanged. No file under src/ changes, no answer changes, and no public name is added, removed or renamed, so no union grows. The version moves in package.json, its only carrier. Documentation takes no changelog fragment here and changelog.d holds only its README, so the 0.6.1 section is written by hand, ruled by the operator, 2026-10-05: dated from the local clock, in the file's existing heading form, placed above 0.6.0's, naming the README's rewrite as an introduction with a documentation map, the three how-to guides and the reference page it links, and the API reference build. The README's install pin moves to the new version. Those are every file a release commit here may touch. Run: the full pnpm gate green on this exact staged tree, and npm pack --dry-run built through the publish guard, which passed and listed 50 files for @riddler/predicator@0.6.1. The tag and the publish are not done here. Refs: pts-g8xs
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.
Prepares the 0.6.1 release of
@riddler/predicator: a patch, and a documentation release that carries 0.6.0's code unchanged.What changes
package.json:versionmoves from 0.6.0 to 0.6.1, its only carrier.CHANGELOG.md: a hand-written## [0.6.1] 2026-10-05section above 0.6.0's, in the file's existing heading form, dated from the local clock. Documentation takes no changelog fragment in this repository andchangelog.d/holds only its README, so there was nothing to promote; the section is written by hand, ruled by the operator, 2026-10-05. It names the README's rewrite as an introduction with a documentation map, the three how-to guides underdocs/guides/, the reference page underdocs/reference/, and the API reference build.README.md: the install pin moves to^0.6.1, as the release recipe and the previous patch prep move it.Those are every file a release commit here may touch (
.claude/wurk/release.md, "The files a release commit touches").Since v0.6.0
Every commit between the
v0.6.0tag and this branch's base touches documentation, docs tooling, the release workflow, a decision record's status or the firewall allowlist. None touchessrc/, so no answer changes and no closed set or public union grows: a patch is the right bump.Checks
pnpm run gateis green on the exact staged tree committed here.npm pack --dry-runran the publish guard, which passed and listed the tarball for@riddler/predicator@0.6.1.The tag and the publish are not done here: once this is merged, the version tag on the merged commit publishes through the release workflow.