Skip to content

chore(release): 1.16.0 - #1745

Merged
Oskar Haarklou Veileborg (BarrensZeppelin) merged 1 commit into
v1.xfrom
npm-publish-v1.16.0
Nov 19, 2026
Merged

Oskar Haarklou Veileborg (BarrensZeppelin) merged 1 commit into
v1.xfrom
npm-publish-v1.16.0

Conversation

@socket-release-bot

Copy link
Copy Markdown
Contributor

Bumps package.json to 1.16.0 and moves the ## [Unreleased] notes under the 1.16.0 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 run approve:npm <stage-id>.

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

@cursor

cursor Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

PR Summary

Low Risk
Release bookkeeping only (version and changelog heading); no runtime or CLI logic changes in the diff.

Overview
Prepares the v1.16.0 npm release by updating release metadata only—no application code changes in this diff.

package.json sets version from 2.1.0-rc.0 to 1.16.0 (still published under the existing publishConfig.tag of rc-2.1.0 unless changed elsewhere).

CHANGELOG.md renames ## [Unreleased] to ## [1.16.0] with the GitHub release link and date 2026-11-19, leaving the existing Added/Changed/Fixed notes under that heading unchanged in this PR.

Reviewed by Cursor Bugbot for commit a3a68d6. Configure here.

@BarrensZeppelin
Oskar Haarklou Veileborg (BarrensZeppelin) merged commit 7034b69 into v1.x Nov 19, 2026
18 of 26 checks passed
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