Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,13 @@

<!-- insert new changelog below this comment -->

## [0.12.5] - 2026-07-03

### Changed

- fix(integrations): cursor-agent honors executable/extra-args env overrides (#3265)
- chore: sync fork with upstream main through 0.12.5 release baseline

## [0.12.4] - 2026-07-02

### Changed
Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[project]
name = "specify-cli"
version = "0.12.5.dev0"
version = "0.12.6.dev0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Preserve a taggable 0.12.5 release commit

When this release change is collapsed to a single tree, there is no commit in the reviewed history whose pyproject.toml version is 0.12.5; the final tree already says 0.12.6.dev0. The release trigger normally commits 0.12.5, tags that commit, then commits the dev bump, and the PyPI workflow checks out the tag and rejects it unless the tag version matches pyproject.toml. If v0.12.5 is placed on this reviewed commit, the publish job will fail with tag 0.12.5 versus package version 0.12.6.dev0, so keep/split the intermediate release-version commit or otherwise ensure the tag points at a tree with version = "0.12.5".

Useful? React with 👍 / 👎.

description = "Specify CLI, part of GitHub Spec Kit. A tool to bootstrap your projects for Spec-Driven Development (SDD)."
readme = "README.md"
requires-python = ">=3.11"
Expand Down
Loading