Skip to content

chore(release): 1.11.1 - #1661

Merged
Martin Torp (mtorp) merged 1 commit into
v1.xfrom
npm-publish-v1.11.1
Oct 27, 2026
Merged

Martin Torp (mtorp) merged 1 commit into
v1.xfrom
npm-publish-v1.11.1

Conversation

@socket-release-bot

@socket-release-bot socket-release-bot Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

Bumps package.json to 1.11.1 and moves the ## [Unreleased] notes under the 1.11.1 heading.

To release:

  1. Review the CHANGELOG section and squash-merge this PR.
  2. Dispatch Publish to npm registry on v1.x with dry-run: false. It tags the merge commit, cuts the GitHub release, and stages all three packages.
  3. Approve each staged package with pnpm stage approve.

If v1.x moves before this merges, re-dispatch with mode: release-pr to rebuild the bump on the new tip.


Note

Low Risk
Version and changelog-only release PR with no runtime code changes in the diff.

Overview
Release 1.11.1 — bumps package.json from 1.11.0 to 1.11.1 and retitles the changelog [Unreleased] section as [1.11.1] (2026-10-27) with the GitHub release link. No application code changes in this diff; it only prepares the npm/GitHub release.

The notes now shipped under 1.11.1 cover Bazel work (SOCKET_BAZEL_OUTPUT_ROOT, Maven extraction on Windows, prerequisite checks, flag quoting, cleanup/timeouts, relative --bazel paths) and broader --dynamic-sbom-inference behavior (every uploaded Maven POM built as its own build, with ignore rules aligned to upload).

Reviewed by Cursor Bugbot for commit 37fde63. Configure here.

@mtorp
Martin Torp (mtorp) merged commit 1dfdd04 into v1.x Oct 27, 2026
12 checks passed
@mtorp
Martin Torp (mtorp) deleted the npm-publish-v1.11.1 branch October 27, 2026 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant