Version Packages

[github-actions]

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

Minor Changes

• e411f9a: A Pipeline tab: every active change in the order it declares, what is
  running right now and whose run it is, and what can be started alongside
  what.

  The placement is derived in core from the readiness report, coordinates
  and all, so the tab and openspec-ui-cli ready cannot disagree and
  nothing in the view is measured. A declared blocker is drawn as a
  relation; a collision is not, because a collision is not an order. A
  cycle of blockers is named rather than placed.

  The readiness report now carries the blockers each change declares, and
  its shape and wording moved to a browser-safe leaf so both surfaces
  describe a collision in the same words.

@openspec-ui/server@1.21.0

Minor Changes

• e411f9a: A Pipeline tab: every active change in the order it declares, what is
  running right now and whose run it is, and what can be started alongside
  what.

  The placement is derived in core from the readiness report, coordinates
  and all, so the tab and openspec-ui-cli ready cannot disagree and
  nothing in the view is measured. A declared blocker is drawn as a
  relation; a collision is not, because a collision is not an order. A
  cycle of blockers is named rather than placed.

  The readiness report now carries the blockers each change declares, and
  its shape and wording moved to a browser-safe leaf so both surfaces
  describe a collision in the same words.

Patch Changes

• Updated dependencies [e411f9a]
  • @openspec-ui/core@0.74.0

@openspec-ui/webui@1.39.0

Minor Changes

• e411f9a: A Pipeline tab: every active change in the order it declares, what is
  running right now and whose run it is, and what can be started alongside
  what.

  The placement is derived in core from the readiness report, coordinates
  and all, so the tab and openspec-ui-cli ready cannot disagree and
  nothing in the view is measured. A declared blocker is drawn as a
  relation; a collision is not, because a collision is not an order. A
  cycle of blockers is named rather than placed.

  The readiness report now carries the blockers each change declares, and
  its shape and wording moved to a browser-safe leaf so both surfaces
  describe a collision in the same words.

Patch Changes

• Updated dependencies [e411f9a]
  • @openspec-ui/core@0.74.0

openspec-ui-vscode@0.50.3

Patch Changes

• Updated dependencies [e411f9a]
  • @openspec-ui/core@0.74.0
  • @openspec-ui/server@1.21.0
  • @openspec-ui/webui@1.39.0