Repository navigation
release: v1.1.1 (canonical schema URL, $comment version, provenance) - #33
Merged
Merged
Conversation
Patch release cutting a real version for the tooling/distribution fixes that landed since v1.1.0: the canonical $id URL is now published (was 404), the schema records its version via $comment, and npm provenance metadata was added. No schema shape change — documents valid against v1.1.0 stay valid. Bumps package.json, schema $comment, :version:, and the README badge to 1.1.1, with a v1.1.1 changelog entry. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
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.
Summary
Cuts a proper v1.1.1 patch for the tooling/distribution fixes that landed after v1.1.0 (canonical
$idURL publishing, schema$commentversion, npm provenance metadata). No schema shape change — documents valid against v1.1.0 remain valid.package.json, schema$comment,.adoc :version:, README badge → 1.1.1Why a version bump
The canonical schema was already deployed via a manual run, but npm + the version-pinned URLs still said 1.1.0. A patch release makes the distribution match the process:
/v1.1.1/ocf-action-v1.jsonpins it, npm gets 1.1.1, and$comment/badge/:version:all agree.Test Plan
$comment,:version:, badge)v1.1.1→ release workflow publishes npm 1.1.1 +/v1.1.1/+ refreshes canonical/schema/v1.jsonFollow-up
Downstream repos (renderer/validator/formations) will be checked to bump their
^1.1.0spec references to^1.1.1where appropriate.🤖 Generated with Claude Code