chore: bump openspec CI pin to 1.5.0 - #7
Merged
Merged
Conversation
@fission-ai/openspec 1.5.0 is the latest release. Bump the CI pin in validate.yml and the matching reference in CLAUDE.md. `validate --strict --all` passes locally under 1.5.0. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
What
Bumps the
@fission-ai/openspecCI pin from1.4.1to1.5.0(the latest release) in.github/workflows/validate.yml, and updates the matching reference inCLAUDE.md.Why
@fission-ai/openspec@1.5.0is the current latest on npm. Keeping the CI pin current keeps the OpenSpec structural-validation gate on the maintained release.Verification
npx @fission-ai/openspec@1.5.0 validate --strict --allpasses locally (3 passed, 0 failed).🤖 Generated with Claude Code