Skip to content

chore(release): 1.13.1 - #1695

Merged
Jeppe Fredsgaard Blaabjerg (jfblaa) merged 1 commit into
v1.xfrom
npm-publish-v1.13.1
Nov 3, 2026
Merged

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

Conversation

@socket-release-bot

@socket-release-bot socket-release-bot Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

Bumps package.json to 1.13.1 and moves the ## [Unreleased] notes under the 1.13.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
Release-only version and changelog edits; no application code changes in the PR diff.

Overview
Prepares v1.13.1 by bumping package.json from 1.13.0 to 1.13.1 and turning the former ## [Unreleased] changelog section into a dated [1.13.1] release entry (with GitHub release link).

The notes under that heading are unchanged in substance: 1.13.1 documents a fix where .NET reachability scans read projects without executing build targets, avoiding failures on compiler-less aggregators such as Microsoft.Build.Traversal. No runtime or CLI code changes appear in this diff—only release metadata.

Reviewed by Cursor Bugbot for commit a9218bc. Configure here.

@jfblaa
Jeppe Fredsgaard Blaabjerg (jfblaa) merged commit 7de3bc7 into v1.x Nov 3, 2026
12 checks passed
@jfblaa
Jeppe Fredsgaard Blaabjerg (jfblaa) deleted the npm-publish-v1.13.1 branch November 3, 2026 16:04
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