Repository navigation
chore(deps): update dependency @fission-ai/openspec to v1.16.0 - #124
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/fission-ai-openspec-1.x
branch
from
November 3, 2026 00:56
ae3b73d to
a409ae1
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 contains the following updates:
1.14.3→1.16.0Release Notes
Fission-AI/OpenSpec (@fission-ai/openspec)
v1.16.0Compare Source
Minor Changes
#2159
33c6f93Thanks @clay-good! - Breaking: the npm package now needs Node.js 22.12.0 or newer. Node 20 reached end-of-life on April 30, 2026. Only npm installs on Node 20 are affected: the standalone binary, the default install since v1.15.0, doesn't use Node, and nothing else about the CLI changes. If you can't upgrade, install the standalone binary (curl -fsSL https://raw.githubusercontent.com/Fission-AI/OpenSpec/main/scripts/binary/install.sh | sh, orirm https://raw.githubusercontent.com/Fission-AI/OpenSpec/main/scripts/binary/install.ps1 | iexon Windows). Homebrew (brew install openspec) still runs on Node, but installs and manages a current Node.js for you as a dependency.#2079
dc37609Thanks @artemasmith! -openspec validatenow warns when aScenario:has no WHEN/GIVEN step or no THEN step, in change deltas and main specs. It is a warning, so plainvalidateandarchiveare unchanged;--strictfails on it.#2077
18a75a5Thanks @micromagicman! - ### Featuresoriginremote, with the--storeflag and thestore:line that select it. OpenSpec only suggests it and never picks a store by name, because repos in different organizations can share a name.Patch Changes
#2131
a6cd3bcThanks @kevin9327! - Stop treating a line that starts with triple-backtick inline code (```npm test```) as a code fence opener, which hid every requirement after it.#2160
d68fc51Thanks @clay-good! - Install from openspec.dev:curl -fsSL https://openspec.dev/cli/install.sh | sh(Windows:irm https://openspec.dev/cli/install.ps1 | iex). Release files are now.tar.gzarchives (.zipon Windows).#2133
cb1adeeThanks @kevin9327! -validatenow reports duplicate or misplaced main-spec requirements written as###Requirement:(no space), matching how archive reads them.#2127
ae7ad75Thanks @clay-good! - ### Bug Fixesopenspec validatenow exits 1 whenopenspec/config.yamlcannot be read or is not valid YAML, instead of passing while every rule in it is ignored. Other commands still warn and carry on.#2172
05cc75fThanks @clay-good! - ### Bug Fixesopenspec completion install zshnow writes its setup to$ZDOTDIR/.zshrcwhenZDOTDIRis set to an absolute path, which is the file zsh actually reads. A relative or~-prefixedZDOTDIRis ignored rather than written relative to the current directory. Before, it created a~/.zshrcthat zsh never loaded, so completion silently didn't work in XDG-style setups such as Home Manager withxdg.enable.completion uninstall zshcleans the same file, and also removes a block an earlier install left in~/.zshrc. If you were affected, runopenspec completion install zshagain: it now adds the block to the right file even when the completion script is already current.v1.15.0Compare Source
Minor Changes
#2137
31c6d1cThanks @clay-good! - OpenSpec now installs as a single file with no Node.js needed:curl -fsSL https://raw.githubusercontent.com/Fission-AI/OpenSpec/main/scripts/binary/install.sh | shon macOS and Linux, orirm https://raw.githubusercontent.com/Fission-AI/OpenSpec/main/scripts/binary/install.ps1 | iexon Windows. Every release now includes binaries for macOS, Linux (glibc and musl) and Windows on x64 and arm64, withSHA256SUMS. npm and the other package managers keep working as before.#2109
c230424Thanks @clay-good! - Addopenspec update --dry-run(with--json) to report the files an update would add, change or delete without writing anything.Patch Changes
#2044
f988c52Thanks @clay-good! -openspec feedbacknow files issues that match the bug form: the body uses the form's headings and spells out the missing repro steps, and the manual-submission link opens the bug form itself with the message, version, and environment prefilled.#2116
15b3b50Thanks @surlymochan! - Commands run with--jsonstart a little faster.status,instructions,new change,templates,validateandschemano longer load theoraspinner package when they are run with--json, which never shows a spinner.openspec status --jsonnow loads 163 modules instead of 186. Output is unchanged.#2120
832e2cfThanks @surlymochan! - ### Bug Fixesopenspec new changeno longer announceswith schema 'spec-driven'in its progress line whenopenspec/config.yamlselects a different schema; the progress line now names the same schema the change is created with.#2114
6b15619Thanks @surlymochan! - ### Bug Fixes/opsx:verifynow matches a REMOVED requirement's baseline by its exact name. After a sync, a similarly named ADDED requirement that replaced it is no longer read as the removed one, so the removal is not reported as still implemented.Configuration
📅 Schedule: (in timezone Asia/Tokyo)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.