Bump @azure-tools/js-sdk-release-tools 2.16.10 → 2.16.11#16224
Merged
Conversation
Co-authored-by: skywing918 <41712999+skywing918@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Bump js-sdk-release-tools version to 2.16.11
Bump @azure-tools/js-sdk-release-tools 2.16.10 → 2.16.11
Jun 30, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR bumps the @azure-tools/js-sdk-release-tools package version from 2.16.10 to 2.16.11, keeping the npm manifest and lockfile in sync for the next release of the tool.
Changes:
- Updated
tools/js-sdk-release-tools/package.jsonpackage version to2.16.11. - Updated
tools/js-sdk-release-tools/package-lock.jsonroot andpackages[""]version entries to2.16.11.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| tools/js-sdk-release-tools/package.json | Bumps the published package version to 2.16.11. |
| tools/js-sdk-release-tools/package-lock.json | Aligns lockfile version metadata with the new package version. |
Files not reviewed (1)
- tools/js-sdk-release-tools/package-lock.json: Generated file
JialinHuang803
approved these changes
Jun 30, 2026
Contributor
|
/check-enforcer override |
3 tasks
skywing918
added a commit
to Azure/azure-sdk-for-js
that referenced
this pull request
Jul 2, 2026
…-tools 2.16.10 → 2.16.12 (#39142) Syncs `eng/tools/js-sdk-release-tools` with [azure-sdk-tools PR #16224](Azure/azure-sdk-tools#16224), which released `@azure-tools/js-sdk-release-tools@2.16.12`. ### What's in 2.16.11 - **Security**: Upgraded `js-yaml` 4.1.1 → 4.2.0 to patch [CVE-2026-53550](GHSA-h67p-54hq-rp68) (quadratic-complexity DoS in merge-key handling) ([#16148](Azure/azure-sdk-tools#16148)) - **Feature**: Added `--report-file` CLI option to `changelogToolCli` for report-only mode — generates a JSON report of SDK changes without modifying `CHANGELOG.md` or bumping the package version ([#16165](Azure/azure-sdk-tools#16165)) - **Fix**: Fix: Import typescript from ts-morph in DifferenceDetector to prevent SyntaxKind mismatch ([#16232](Azure/azure-sdk-tools#16232)) ### Changes - `package.json`: `@azure-tools/js-sdk-release-tools` `2.16.10` → `2.16.12` - `package-lock.json`: regenerated ### Packages impacted by this PR `eng/tools/js-sdk-release-tools` ### Issues associated with this PR Closes #39141 ### Describe the problem that is addressed by this PR `eng/tools/js-sdk-release-tools/package.json` was pinned to `@azure-tools/js-sdk-release-tools@2.16.10`; needs to track the latest release (2.16.11). ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? N/A — version pin update only. ### Are there test cases added in this PR? _(If not, why?)_ No — dependency version bump; test coverage lives in upstream `azure-sdk-tools`. ### Provide a list of related PRs _(if any)_ - Azure/azure-sdk-tools#16224 - Azure/azure-sdk-tools#16148 - Azure/azure-sdk-tools#16165 - Azure/azure-sdk-tools#16232 ### Checklists - [x] Added impacted package name to the issue description. - [ ] Does this PR need any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here.)_ - [ ] Added a changelog (if necessary). --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: skywing918 <41712999+skywing918@users.noreply.github.com> Co-authored-by: Kyle Zhang <v-zhanh@microsoft.com>
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.
Bumps the @azure-tools/js-sdk-release-tools package version from 2.16.10 to 2.16.11.
Changelog
Related js-sdk-release-tools PRs merged since the last version bump (2.16.10):
#16148 — fix: upgrade js-yaml to 4.2.0 to patch CVE-2026-53550 (GHSA-h67p-54hq-rp68)
#16165 — Changelog generation for JSON output without modifying CHANGELOG.md
Changes
tools/js-sdk-release-tools/package.json — version field updated to 2.16.11
tools/js-sdk-release-tools/package-lock.json — root and packages[""] version entries updated to 2.16.11