Skip to content

Version Packages - #842

Merged
VeryComplexAndLongName merged 1 commit into
mainfrom
changeset-release/main
Oct 7, 2026
Merged

VeryComplexAndLongName merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish 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

@openspec-ui/core@0.137.0

Minor Changes

  • 4b1cfa2: Agents are told how work is done here (agents-are-told-how-work-is-done-here, ADR 0043). Initializing OpenSpec, in either host, now writes a section into CLAUDE.md and AGENTS.md that tells every agent, however it was started, to work each change in a git worktree of its own at ../.worktrees// on a branch cut from origin/main, and where the stage assignment is; a file somebody else wrote gets it only where you agree. "Write Agent Workflow Rules" adds it to a repository initialized before. "Create OpenSpec Change" now makes the change in its own working directory, and openspec-ui-cli worktree add makes one for a change that does not exist yet. Initializing also offers to commit the OpenSpec setup to main and push it at once, so each change has origin/main to be cut from; an agent that finds it missing commits it itself and goes on.
  • ae5156f: What landed is archived without waiting (landed-changes-are-archived-without-waiting). The extension now starts in any workspace with an OpenSpec project, not only once its view is opened, so the sweep that archives landed changes runs there. A host sweeps again within minutes, not at its half hour, after an archive merges, after a new failure, and while a change's own branch is on the server, so a merge is followed by its archive within minutes. A refused push says git's reason, and a fetch that failed says the archive waits.

openspec-ui-vscode@0.95.0

Minor Changes

  • 4b1cfa2: Agents are told how work is done here (agents-are-told-how-work-is-done-here, ADR 0043). Initializing OpenSpec, in either host, now writes a section into CLAUDE.md and AGENTS.md that tells every agent, however it was started, to work each change in a git worktree of its own at ../.worktrees// on a branch cut from origin/main, and where the stage assignment is; a file somebody else wrote gets it only where you agree. "Write Agent Workflow Rules" adds it to a repository initialized before. "Create OpenSpec Change" now makes the change in its own working directory, and openspec-ui-cli worktree add makes one for a change that does not exist yet. Initializing also offers to commit the OpenSpec setup to main and push it at once, so each change has origin/main to be cut from; an agent that finds it missing commits it itself and goes on.

Patch Changes

  • ae5156f: What landed is archived without waiting (landed-changes-are-archived-without-waiting). The extension now starts in any workspace with an OpenSpec project, not only once its view is opened, so the sweep that archives landed changes runs there. A host sweeps again within minutes, not at its half hour, after an archive merges, after a new failure, and while a change's own branch is on the server, so a merge is followed by its archive within minutes. A refused push says git's reason, and a fetch that failed says the archive waits.
  • Updated dependencies [4b1cfa2]
  • Updated dependencies [ae5156f]
    • @openspec-ui/core@0.137.0
    • @openspec-ui/server@1.56.0
    • @openspec-ui/webui@1.84.0

@openspec-ui/server@1.56.0

Minor Changes

  • 4b1cfa2: Agents are told how work is done here (agents-are-told-how-work-is-done-here, ADR 0043). Initializing OpenSpec, in either host, now writes a section into CLAUDE.md and AGENTS.md that tells every agent, however it was started, to work each change in a git worktree of its own at ../.worktrees// on a branch cut from origin/main, and where the stage assignment is; a file somebody else wrote gets it only where you agree. "Write Agent Workflow Rules" adds it to a repository initialized before. "Create OpenSpec Change" now makes the change in its own working directory, and openspec-ui-cli worktree add makes one for a change that does not exist yet. Initializing also offers to commit the OpenSpec setup to main and push it at once, so each change has origin/main to be cut from; an agent that finds it missing commits it itself and goes on.

Patch Changes

  • Updated dependencies [4b1cfa2]
  • Updated dependencies [ae5156f]
    • @openspec-ui/core@0.137.0

@openspec-ui/webui@1.84.0

Minor Changes

  • 4b1cfa2: Agents are told how work is done here (agents-are-told-how-work-is-done-here, ADR 0043). Initializing OpenSpec, in either host, now writes a section into CLAUDE.md and AGENTS.md that tells every agent, however it was started, to work each change in a git worktree of its own at ../.worktrees// on a branch cut from origin/main, and where the stage assignment is; a file somebody else wrote gets it only where you agree. "Write Agent Workflow Rules" adds it to a repository initialized before. "Create OpenSpec Change" now makes the change in its own working directory, and openspec-ui-cli worktree add makes one for a change that does not exist yet. Initializing also offers to commit the OpenSpec setup to main and push it at once, so each change has origin/main to be cut from; an agent that finds it missing commits it itself and goes on.

Patch Changes

  • Updated dependencies [4b1cfa2]
  • Updated dependencies [ae5156f]
    • @openspec-ui/core@0.137.0

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from d49a023 to 393d1c3 Compare October 7, 2026 20:12
@VeryComplexAndLongName
VeryComplexAndLongName merged commit 820a7d9 into main Oct 7, 2026
10 checks passed
@VeryComplexAndLongName
VeryComplexAndLongName deleted the changeset-release/main branch October 7, 2026 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant