Repository navigation
chore: bump version to 7.2.0 - #241
Merged
Merged
Conversation
John-David Dalton (jdalton)
force-pushed
the
npm-publish-v7.2.0
branch
from
October 19, 2026 00:49
7977045 to
93c479b
Compare
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
1 participant
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.
This signed release reservation was created by the npm publish workflow. Squash-merge this PR with its title unchanged. Then dispatch the npm publish workflow from the default branch with resume-publish set to true.
Note
Low Risk
Version and changelog-only release PR with minor lockfile workspace cleanup; no runtime library code changes in the diff.
Overview
Release 7.2.0 — bumps
@socketsecurity/libfrom7.1.1to7.2.0and adds the 7.2.0 changelog section (2026-10-18).The new notes summarize work already landed on the branch: release fixes (skip model setup for explicit targets, resume from reserved bump source, hosted npm runner), node compatibility (Node 18.20.8, npm 10, array primordials), and ci housekeeping (publish coverage tracking, workflow gates, dropping the consumer freshness gate, moving quality audits to follow-ups).
pnpm-lock.yamldrops importers for two fleet hook workspaces (setup-signing,unbacked-claim-guard), aligning the lockfile with those gitignored hook packages no longer participating in the workspace graph.Reviewed by Cursor Bugbot for commit 4f2ff4e. Configure here.