release: v1.10.0#52
Merged
Merged
Conversation
Minor release. Since v1.9.1 the default branch gained the `update` input (#46/#51, a backward-compatible additive feature) plus the .zip bundle-detection fix (#47) and routine dependency bumps (#48, #28, #50). - package.json / package-lock.json: 1.9.1 -> 1.10.0 - CHANGELOG: cut [1.10.0] from [Unreleased]; add the missing Fixed entry for .zip archive detection (#47), which was merged without a changelog line. The `update` input Added entry carries over. dist/ verified clean (no drift) after a fresh `npm run build`; the version bump is not embedded in the bundle. typecheck, lint, and the full 195-test suite pass. 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 v1.10.0 release by bumping the npm package version and promoting the previously merged update input feature and .zip bundle-detection fix into the changelog for a minor release.
Changes:
- Bump package version 1.9.1 → 1.10.0 in
package.jsonandpackage-lock.json. - Cut a new [1.10.0] - 2026-06-25 section in
CHANGELOG.md. - Add the previously-missing changelog entry documenting the
.ziparchive detection fix, plus supporting reference links.
Show a summary per file
| File | Description |
|---|---|
| package.json | Updates the package version to 1.10.0 for the release. |
| package-lock.json | Keeps the lockfile’s top-level and root package versions in sync at 1.10.0. |
| CHANGELOG.md | Adds the 1.10.0 release notes and missing .zip detection fix entry with link references. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- 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.
TL;DR
Cut v1.10.0 (minor). Since v1.9.1,
maingained theupdateinput feature (#46/#51) plus the.zipbundle-detection fix (#47) and routine dependency bumps. A new backward-compatible input mandates a minor bump;@v1consumers auto-heal on the tag push.What changed
package.json/package-lock.json:1.9.1 -> 1.10.0CHANGELOG.md: cut[1.10.0]from[Unreleased]; add the missing### Fixedentry for.ziparchive detection (fix(bundler): accept .zip archives produced by apm pack (apm 0.20+) #47) — that fix was merged without a changelog line. Theupdate-input### Addedentry carries over.Why this matters now
The
.zipfix (#47) unblocks the GH-AW Compatibility job inmicrosoft/apmreleases:apm pack --archivedefaults to.zipat apm >= 0.20 (microsoft/apm#1720), and that job runs withapm-version= the apm release tag (currently 0.21.0). Pre-fix@v1only detected.tar.gzand failed. Releasing v1.10.0 and movingv1lands the fix for@v1consumers.Validation
npm run typecheckcleannpm run lintcleannpm run buildclean;dist/has no drift after a fresh build (version bump is not embedded in the bundle)npm test: 195 passed, 5 suitesRelease mechanics (post-merge)
After merge, pushing tag
v1.10.0triggersci.yml's release job: force-moves the floatingv1tag and publishes a GitHub release. Nov2; no downstream break.Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com