Repository navigation
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This branch has not been deployed
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.16.0→2.0.0Release Notes
Fission-AI/OpenSpec (@fission-ai/openspec)
v2.0.0Compare Source
Major Changes
#2223
d97d7e2Thanks @clay-good! - OpenSpec 2.0 installs skills only, in one shared folder. Runopenspec updatein 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./opsx:*command files. Each command has a skill with the same instructions. For example,/opsx:proposebecomesopenspec-propose, which you invoke as/openspec-propose($openspec-proposein Codex).openspec updateremoves the command files earlier versions generated, and keeps and lists any you edited..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 ownskills/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.deliveryis retired. It is still accepted, so older configs and scripts keep working, but it no longer changes anything.openspec updateremoves the files OpenSpec wrote in.amazonq/(keeping any you edited), and--tools amazon-qnow points you to Kiro.git config --global core.symlinks true(or clone withgit 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, whichopenspec updatereplaces with a plain copy of the skill.Patch Changes
#2229
5cd4f7fThanks @clay-good! - On Windows,openspec completion installrun 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
a959be7Thanks @clay-good! - Read a task that wraps onto several lines in tasks.md as one task.openspec instructions applyused 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.0Compare Source
Minor Changes
9ca6b77Thanks @clay-good! - Command files are deprecated and go away in OpenSpec 2.0; your skills stay and do the same work.openspec updatenow says so, with the one command to switch early:openspec config set delivery skills && openspec update. Details in #2022.Patch Changes
#2213
9ca6b77Thanks @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
9ca6b77Thanks @clay-good! -openspec updatenow 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.1Compare Source
Patch Changes
#2205
c887ab0Thanks @clay-good! -validate,show,list,viewandarchivenow read section headings written with a CommonMark closing#run (## Purpose ##,## Why ##,## What Changes ##,## Requirements ##,## ADDED Requirements ##) the same as their unclosed forms.#2206
a1ae536Thanks @clay-good! -openspec version --checkon the standalone binary now offers only a release whose files are attached on GitHub, the same oneopenspec installwould install, instead of a version npm has but the installer cannot get yet.#2207
83053ddThanks @clay-good! -validatenow fails, andarchiverefuses, when a delta spec puts a requirement under an unrecognized## ... Requirementssection such as## DEPRECATED Requirements, instead of passing with a warning and silently dropping that requirement.#2204
ef170faThanks @clay-good! -openspec version --checknow checks for a newer version even when telemetry is turned off or it runs in CI; onlyOPENSPEC_NO_UPDATE_CHECKskips it, and the background check inopenspec updatestill honors the telemetry opt-out and CI.Configuration
📅 Schedule: (UTC)
🚦 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 has been generated by Mend Renovate CLI.