Skip to content

chore(release): 1.6.0 - #1586

Merged
Jeppe Fredsgaard Blaabjerg (jfblaa) merged 1 commit into
v1.xfrom
npm-publish-v1.6.0
Oct 7, 2026
Merged

Jeppe Fredsgaard Blaabjerg (jfblaa) merged 1 commit into
v1.xfrom
npm-publish-v1.6.0

Conversation

@socket-release-bot

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

Copy link
Copy Markdown

Bumps package.json to 1.6.0 and moves the ## [Unreleased] notes under the 1.6.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 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 bump with no runtime code changes.

Overview
Release 1.6.0 — bumps the published CLI version from 1.5.0 to 1.6.0 in package.json and adds a dated ## [1.6.0] section to CHANGELOG.md (2026-10-07).

The new changelog entry documents the shipped feature: manifest now attributes direct JVM dependencies to the subproject build files that declare them (#1581). No application code changes in this PR.

Reviewed by Cursor Bugbot for commit 01763d0. Configure here.

@jfblaa
Jeppe Fredsgaard Blaabjerg (jfblaa) merged commit 23d1a62 into v1.x Oct 7, 2026
16 checks passed
@jfblaa
Jeppe Fredsgaard Blaabjerg (jfblaa) deleted the npm-publish-v1.6.0 branch October 7, 2026 12:46
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