chore: release v0.18.0#1661
Merged
Merged
Conversation
Bump pyproject.toml and uv.lock to 0.18.0 and move the [Unreleased] CHANGELOG block to [0.18.0] - 2026-06-04 with one entry per merged PR since v0.17.0. Lint mirror (ruff check + format, pylint R0801, auth-signals) verified green locally. Post-merge: tag v0.18.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
Cut release v0.18.0 by bumping the project version and rolling the changelog forward from [Unreleased] into a dated release section.
Changes:
- Bump
apm-cliversion to0.18.0inpyproject.toml. - Update
uv.lockto reflect the newapm-cliversion. - Add a
0.18.0section inCHANGELOG.mdwith entries for merged PRs since0.17.0.
Show a summary per file
| File | Description |
|---|---|
pyproject.toml |
Version bump to 0.18.0. |
uv.lock |
Lockfile updated to match the new project version. |
CHANGELOG.md |
Adds the 0.18.0 release notes section and moves content out of Unreleased. |
Copilot's findings
- Files reviewed: 2/3 changed files
- Comments generated: 8
Comment on lines
+14
to
+16
| - `apm marketplace audit`: new command that flags dependencies bypassing | ||
| marketplace pinning, so you can catch unpinned or non-marketplace deps before | ||
| they ship. (by @edenfunf, #881) |
Comment on lines
17
to
+20
| - Marketplace dependency object entries in `apm.yml` and `plugin.json` now | ||
| resolve to concrete git refs during install, support optional semver-style | ||
| `version` constraints, and fail closed when resolution errors occur - by | ||
| @stbenjam (#1422) | ||
| `version` constraints, and fail closed when resolution errors occur. (by | ||
| @stbenjam, #1422) |
Comment on lines
+21
to
+23
| - LSP server management: declare language servers in `apm.yml` and `apm install` | ||
| wires them into Claude Code and GitHub Copilot CLI automatically. (by | ||
| @stbenjam, #1424) |
Comment on lines
+24
to
+26
| - `apm outdated` now recognizes monorepo `{name}-v{version}` tag naming, so | ||
| per-package version checks work in repositories that publish multiple packages | ||
| under subpath tags. (by @kevinbeier-enbw, #1504) |
Comment on lines
+36
to
+38
| - `apm compile` now matches `applyTo` globs without following symlinks into | ||
| `node_modules`, avoiding spurious matches and slow traversals in projects with | ||
| symlinked dependencies. (by @srid, #1576) |
Comment on lines
+39
to
+41
| - `apm install` now rewrites outbound relative links inside skill bundles so the | ||
| links keep resolving after a skill is materialized into an agent target. | ||
| (closes #1625, #1657) |
Comment on lines
42
to
+45
| - Git-source semver ranges for virtual subdirectory dependencies now match | ||
| per-package `{name}-v{version}` tags, derive `{name}` from the subpath, and | ||
| reject malformed range-like refs with an actionable manifest error. (#1658) | ||
|
|
||
| ### Breaking | ||
|
|
||
| - Reject string-form `@alias` dependency shorthand at parse time with a migration error; use object form with `alias:` instead -- by @prateek (#1301) | ||
|
|
||
| ### Added | ||
|
|
||
| - LSP server management: declare language servers in `apm.yml` and `apm install` wires them into Claude Code and GitHub Copilot CLI automatically -- by @stbenjam (#1424) | ||
| reject malformed range-like refs with an actionable manifest error. (closes | ||
| #1633, #1658) |
Comment on lines
+46
to
+48
| - `apm install` now preserves env-var placeholders (e.g. `${VAR}`) when writing | ||
| IntelliJ `mcp.json`, so configured environment references survive install | ||
| instead of being expanded or dropped. (closes #1656, #1659) |
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.18.0.
pyproject.tomlto 0.18.0 (anduv.lock).[Unreleased]to[0.18.0] - 2026-06-04inCHANGELOG.md, with one short "so what?" entry per PR merged since v0.17.0.Why MINOR (0.18.0), not PATCH (0.17.1)
The cycle contains a BREAKING change (#1655,
@aliasshorthand rejected at parse time) plus new user-facing surface: a newapm marketplace auditcommand (#881), marketplace dependency objects inplugin.json(#1422), first-class LSP server support (#1424), and monorepo tag-naming support inapm outdated(#1504). Any of the latter alone forces a minor bump; pre-1.0, the breaking change rides in the minor rather than triggering a 1.0.Breaking changes
apmrejects string-form@aliasdependency shorthand at parse time (fix(deps): reject shorthand alias syntax (supersedes #1301) #1655). Migrate to the object form withalias:. Marked**BREAKING:**in the changelog.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.18.0to trigger the release workflow: