chore: release v0.20.0#1756
Merged
Merged
Conversation
Bump pyproject.toml + uv.lock to 0.20.0 and roll the [Unreleased] CHANGELOG block into [0.20.0] - 2026-06-11. Lint mirror green locally (ruff check + format, pylint R0801, auth-signals). Post-merge: tag v0.20.0 to trigger the release workflow. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR cuts the v0.20.0 release by updating the package version and rolling the changelog forward from [Unreleased] to a dated 0.20.0 section.
Changes:
- Bump
apm-cliversion from0.19.0to0.20.0inpyproject.toml. - Update the local editable package entry in
uv.lockto0.20.0. - Move release notes into
## [0.20.0] - 2026-06-11inCHANGELOG.md(including adding the missing(#1726)reference on the Hermes entry).
Show a summary per file
| File | Description |
|---|---|
pyproject.toml |
Updates project version to 0.20.0. |
uv.lock |
Updates the editable apm-cli lock entry to 0.20.0. |
CHANGELOG.md |
Creates the 0.20.0 release section dated 2026-06-11 and attributes Hermes entry to PR #1726. |
Copilot's findings
- Files reviewed: 2/3 changed files
- Comments generated: 0
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.
Cut release 0.20.0.
pyproject.tomlto 0.20.0 (anduv.lock).[Unreleased]to[0.20.0] - 2026-06-11inCHANGELOG.md, with one short "so what?" entry per PR merged since v0.19.0.Why MINOR (0.20.0), not PATCH (0.19.1)
Multiple MINOR signals fired this cycle: two new experimental targets (
apm install --target kiro#1741,--target hermes#1726), enterprise bootstrap mirror mode (#1733), a newapm pack --archive-formatflag (#1720), a newsourceBasemarketplace manifest field (#1736), newapm marketplace addsource kinds (#1739), SHA-pin auto-update (#1738), and git-transport path fetching (#1740). The remaining PRs are bug fixes subordinate to those signals.Pre-1.0 framing keeps this a MINOR (not MAJOR): the one breaking change rides in a minor bump.
BREAKING this cycle:
apm pack --archivenow produces.zipby default instead of.tar.gz(#1720), matchingapm publishoutput and plugin-host expectations. Use--archive-format tar.gzto opt back in.Validation
Lint mirror green locally (ruff check + format, pylint R0801, auth-signals). See
.apm/instructions/linting.instructions.mdfor the contract this mirrors.Post-merge
Tag
v0.20.0to trigger the release workflow: