Skip to content

⬆️ chore(deps): update dependency @fission-ai/openspec to v2 - #545

Open
konih wants to merge 1 commit into
mainfrom
renovate/fission-ai-openspec-2.x
Open

konih wants to merge 1 commit into
mainfrom
renovate/fission-ai-openspec-2.x

Conversation

@konih

@konih konih commented Nov 12, 2026

Copy link
Copy Markdown
Collaborator

This PR contains the following updates:

Package Change Age Confidence
@fission-ai/openspec 1.16.0 → 2.0.0 age confidence

Release Notes

Fission-AI/OpenSpec (@​fission-ai/openspec)

v2.0.0

Compare Source

Major Changes
  • #​2223 d97d7e2 Thanks @​clay-good! - OpenSpec 2.0 installs skills only, in one shared folder. Run openspec update in each project to move it over. Old command files and old skill copies you edited are kept. An edit inside a skill OpenSpec installs in .agents/skills/ is replaced, as in 1.x, so save those first. See Upgrade to 2.0.

    • Skills only. OpenSpec no longer writes /opsx:* command files. Each command has a skill with the same instructions. For example, /opsx:propose becomes openspec-propose, which you invoke as /openspec-propose ($openspec-propose in Codex). openspec update removes the command files earlier versions generated, and keeps and lists any you edited.
    • One shared copy. Skills are written once, to .agents/skills/, instead of a copy per tool. Claude Code, Continue, ForgeCode, Kiro, CodeBuddy, EasyCode, iFlow, CodeArts, Lingma, GigaCode, Veai, Rovo Dev, Code Studio and Hermes Agent get a link to each skill in their own skills/ folder (a plain copy where a link can't be made). MiniMax Code is the exception: its skills go to ~/.minimax/skills/. Old per-tool copies are removed, or kept and reported if you edited them.
    • delivery is retired. It is still accepted, so older configs and scripts keep working, but it no longer changes anything.
    • Amazon Q Developer is retired. It can't load skills. openspec update removes the files OpenSpec wrote in .amazonq/ (keeping any you edited), and --tools amazon-q now points you to Kiro.
    • Windows. To check out committed links, run git config --global core.symlinks true (or clone with git clone -c core.symlinks=true <url>) and enable Developer Mode so links can be created. Otherwise each link checks out as a small text file, which openspec update replaces with a plain copy of the skill.
Patch Changes
  • #​2229 5cd4f7f Thanks @​clay-good! - On Windows, openspec completion install run from cmd.exe no longer edits your PowerShell profiles. OpenSpec now tells cmd.exe and PowerShell apart, says cmd.exe isn't supported, and stops suggesting the completion tip there.

  • #​2228 a959be7 Thanks @​clay-good! - Read a task that wraps onto several lines in tasks.md as one task. openspec instructions apply used to cut a wrapped task off at its first line break; it now returns the full text, including lines continued with a trailing \.

v1.17.0

Compare Source

Minor Changes
  • #​2213 9ca6b77 Thanks @​clay-good! - Command files are deprecated and go away in OpenSpec 2.0; your skills stay and do the same work. openspec update now says so, with the one command to switch early: openspec config set delivery skills && openspec update. Details in #​2022.
Patch Changes
  • #​2213 9ca6b77 Thanks @​clay-good! - Switching to skills only (openspec config set delivery skills) no longer deletes command files you edited. Only files OpenSpec generated are removed; edited ones are kept and listed.

  • #​2213 9ca6b77 Thanks @​clay-good! - openspec update now upgrades a project from any release since 0.12 in one run. It removes old OpenSpec files nobody edited, without needing --force, and keeps any you changed. It never touches files outside the project, even through a linked folder.

v1.16.1

Compare Source

Patch Changes
  • #​2205 c887ab0 Thanks @​clay-good! - validate, show, list, view and archive now read section headings written with a CommonMark closing # run (## Purpose ##, ## Why ##, ## What Changes ##, ## Requirements ##, ## ADDED Requirements ##) the same as their unclosed forms.

  • #​2206 a1ae536 Thanks @​clay-good! - openspec version --check on the standalone binary now offers only a release whose files are attached on GitHub, the same one openspec install would install, instead of a version npm has but the installer cannot get yet.

  • #​2207 83053dd Thanks @​clay-good! - validate now fails, and archive refuses, when a delta spec puts a requirement under an unrecognized ## ... Requirements section such as ## DEPRECATED Requirements, instead of passing with a warning and silently dropping that requirement.

  • #​2204 ef170fa Thanks @​clay-good! - openspec version --check now checks for a newer version even when telemetry is turned off or it runs in CI; only OPENSPEC_NO_UPDATE_CHECK skips it, and the background check in openspec update still honors the telemetry opt-out and CI.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@konih konih added the dependencies Pull requests that update a dependency file label Nov 12, 2026
@sonarqubecloud

Copy link
Copy Markdown

@codecov

codecov Bot commented Nov 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants