Skip to content

chore: release 0.12.5, begin 0.12.6.dev0 development#52

Open
bigsmartben wants to merge 2 commits into
mainfrom
chore/release-v0.12.5
Open

chore: release 0.12.5, begin 0.12.6.dev0 development#52
bigsmartben wants to merge 2 commits into
mainfrom
chore/release-v0.12.5

Conversation

@bigsmartben

Copy link
Copy Markdown
Owner

Automated release of 0.12.5.

The git tag v0.12.5 has been pushed and the release artifacts are being built from that tag.

Merging this PR will set main to 0.12.6.dev0 so development installs are marked as pre-release.

Assisted-by: Codex (model: GPT-5, autonomous), acting on behalf of @bigsmartben.

Assisted-by: Codex (model: GPT-5, autonomous)
Assisted-by: Codex (model: GPT-5, autonomous)

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 81a4843486

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread pyproject.toml
[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 👍 / 👎.

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