chore(release): version packages - #1488
Open
openspec-release-bot[bot] wants to merge 1 commit into
Open
Conversation
openspec-release-bot
Bot
requested review from
clay-good
and removed request for
a team
July 29, 2026 22:47
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.8.0
Minor Changes
1aa0f2aThanks @solanab! - Add the vendor-neutralagentstarget:openspec init --tools agentsinstalls the workflow skills to.agents/skills/openspec-*/SKILL.md, the shared location AGENTS.md-compatible assistants read. It is skills-only, so no slash commands are generated. Becauseagentsis now a real target,--tools allincludes it and creates.agents/skills/where it previously did not.Patch Changes
#1486
427abf4Thanks @clay-good! - Task progress now counts indented sub-tasks. Atasks.mdwhose sub-tasks were unfinished reported✓ Completeinopenspec listandopenspec view, was missing those tasks from theopenspec instructions applylist, and archived with no incomplete-task warning, because both checkbox parsers only matched checkboxes at column 0.Progress counting and the apply task list now share one parser, so
list,view,archiveandapplyagree about which lines of a tasks file are tasks. A checkbox with no text after it is left out of the apply list, which has nothing to act on, but still counts toward every progress number; a file of nothing but such checkboxes now asks to be rewritten rather than reporting itself done. The shared pattern matches every line the two it replaced matched, and more, so task counts can rise but never fall: no change starts reporting less work than before, and archive's incomplete-task warning can only become stricter. Checkboxes are still counted wherever they appear, including inside a code fence, an HTML comment or an indented block, so atasks.mdthat shows a checklist as a format example can now count that example as work — remove it from the file, or pass--yesto archive.#1482
84ebc57Thanks @clay-good! -openspec validate <change>now reports a MODIFIED requirement that omits a scenario the main spec still has — the same loss archive already refuses to apply — so the change fails at authoring time instead of at archive time. A change carrying a stale MODIFIED block will start failing validation; it was already unarchivable, and the message names the scenarios to copy back in.