chore(release): version packages#1295
Open
openspec-release-bot[bot] wants to merge 1 commit into
Open
Conversation
openspec-release-bot
Bot
force-pushed
the
changeset-release/main
branch
from
4789676 to
b96316e
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@fission-ai/openspec@1.5.1
Patch Changes
#1280
a325305Thanks @clay-good! - ### Bug Fixesvalidateresolves changes likestatus—openspec validate <change>(and--all/--changesand the interactive selector) now resolves a change by directory existence, matchingstatus/instructions, instead of requiringproposal.md. A scaffolded or still-authoring change is validated rather than reported asUnknown item, and a resolved-but-invalid change now exits non-zero. Delta discovery also recurses the nestedspecs/<area>/<capability>/spec.mdlayout. (openspec validate cannot resolve changes in a workspace planning home #1182)tasks.md—openspec view,list, and thearchiveincomplete-task gate now resolve task progress through the tracked-tasks artifact'sgeneratesglob (the same file-resolutionstatususes), so a change whose tasks live in nestedtasks.mdfiles is classified correctly and can no longer archive while unfinished. (Feedback: openspec view does not detect nested tasks.md files #1202)### Requirement:header now receives the same targeted "move it to the body line" remediation as a change delta, emitted exactly once. (1.4.0 clearer SHALL/MUST hint does not apply to main specs #1156)