Repository navigation
chore: release 1.2.1, begin 1.2.2.dev0 development - #4996
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
馃煝 Approval recommended
Both changes are limited to release metadata and match the stated release process.
0 open findings
What changed in this PR
Records the Spec Kit 1.2.1 release and prepares Specify CLI for the next development cycle.
Changes:
- Adds the 1.2.1 changelog entry.
- Advances the development version to
1.2.2.dev0.
| File | Description |
|---|---|
| pyproject.toml | Sets the next development version. |
| CHANGELOG.md | Records changes released in 1.2.1. |
馃 Review effort: Max
馃挕 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Automated release of 1.2.1.
This PR was created by the Release Trigger workflow. The git tag
v1.2.1has already been pushed and the release artifacts are being built.Merging this PR will set
mainto1.2.2.dev0so that development installs are clearly marked as pre-release.