chore(tooling): adopt specification validator v1.2.0 - #12
Merged
Conversation
Pin repository verification to the current immutable tooling release. Keep configuration, workflow, and changelog metadata aligned. Impact: none
Record the exact authority, evidence, interoperability, and change control for every required JSON:API decision. Narrow the declared protocol version to the package's actual 1.1 contract. Impact: none
Bind every observable JSON:API and referenced RFC choice to immutable sources, separate update monitoring, and executable evidence. Keep the maintained peer outside the public module while recording classified differential results. Impact: none
Run the canonical decision validator so CI fails on missing, stale, contradictory, or untested specification choices. Impact: none
Keep workflow and CLI tooling on v1.0.13 until the specification validator is published at an immutable release identity. Impact: none
Expect the pending first array item path for a truncated array, matching the existing object-member contract and scanner behavior. Impact: none
The supported toolchain reports a truncated empty array at its parent path. Keep the defensive decoder expectation aligned with that contract.
The canonical validator commit is now available to hosted workflows. Pin both identities so JSON:API uses the ecosystem-wide release gate.
Bind local and hosted verification to the same immutable released validator. Preserve the repository-owned specification-governance evidence. Impact: none
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.
Integrate the repository's specification decisions and adopt go-library-tools v1.2.0 for the same released validator in local and hosted checks.
The immutable workflow pin preserves the reviewed validator lineage while the release checksum binds the downloaded CLI.