docs(changelog): cut 1.7.1#37
Merged
Merged
Conversation
Patch release wrapping #36: completes the v0.12.3 strict-detection fix for the non-isolated additive install path that v1.7.0 missed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds the v1.7.1 changelog entry so the release workflow can publish a patch release that includes the non-isolated additive apm install --target forwarding fix from #36.
Changes:
- Add a
1.7.1section documenting the fix for forwardingtargetto additive (non-isolated)apm installcalls. - Add a PR reference link for #36 in the changelog entry.
Show a summary per file
| File | Description |
|---|---|
| CHANGELOG.md | Adds the v1.7.1 release notes describing the additive install --target forwarding fix (PR #36). |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 1
Comment on lines
+11
to
+17
| ## [1.7.1] - 2026-05-07 | ||
|
|
||
| ### Fixed | ||
|
|
||
| - **Forward `target` input to additive `apm install` invocations** ([#36]). v1.7.0 fixed the isolated-mode path but missed the non-isolated additive path (`apm install <dep>` per inline dep, no `apm.yml` present), which still hit APM v0.12.3 strict harness detection (exit 2, "No harness detected") on any workspace without an on-disk marker. `installDeps()` now appends `--target <value>` to every per-dep call, mirroring what isolated mode achieves via the generated `apm.yml`. | ||
|
|
||
| [#36]: https://github.com/microsoft/apm-action/pull/36 |
4 tasks
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.
Patch release wrapping #36.
v1.7.0 fixed the isolated-mode strict-detection break (#33) and hardened input validation (#34), but missed the non-isolated additive install path. #36 completes the coverage; this PR adds the CHANGELOG entry so the release workflow has something to publish.
After merge: tag
v1.7.1frommain, release workflow auto-moves the floatingv1tag forward (currently still pointing at the broken v1.7.0 for the additive path).