chore(release): set version to 2026.06.1 [release:2026.06.1] - #21
Closed
tcballard wants to merge 1 commit into
Closed
chore(release): set version to 2026.06.1 [release:2026.06.1]#21tcballard wants to merge 1 commit into
tcballard wants to merge 1 commit into
Conversation
Second release. Bumps package.json to the zero-padded CalVer 2026.06.1 (the workflow de-pads to 2026.6.1 for npm) and adds the 2026.06.1 CHANGELOG entry — the graph schema_version compatibility check, plus the move to OIDC publishing. Cut a GitHub Release tagged 2026.06.1 to publish (requires the npm trusted publisher configured for release.yml). Signed-off-by: Tom Ballard <tom@armytage.co>
Contributor
Author
|
Superseded by #26, which releases 2026.07.1 — that cut folds in the schema-version guard and everything since (the OpenAI-compatible adapter, browser-extension verification, and the Dogfood self-coverage gate). Closing this in favour of 2026.07.1. Generated by Claude Code |
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.
Why
Stages the second release.
mainnow carries the graphschema_versioncompatibility check (#20) and the OIDC release workflow (#19), so this bumps the version and writes the release entry.What
package.json→2026.06.1(padded; the workflow de-pads to2026.6.1for npm).CHANGELOG.md→ the2026.06.1— "contract guard" entry (the schema-version guarantee; note on the move to Trusted Publishing).Release sequence (after merge)
@itsthelore/proofkeeper(orgitsthelore, repoproofkeeper, workflowrelease.yml, actionnpm publish) — required, since the workflow is now tokenless OIDC.2026.06.1targetingmain.2026.6.1and publishes via OIDC with automatic provenance.Config/docs only — no application code changed.