Skip to content

Conversation

@jdalton
Copy link
Contributor

@jdalton jdalton commented Jan 26, 2026

Summary

The update script was only updating @socketsecurity/*, @socketregistry/*, and @socketbin/* packages when the --apply flag was passed. This meant newly released Socket packages within taze's 7-day maturity period were being skipped during regular pnpm run update runs.

Changes

  • Removed the if (apply) condition around Socket package updates
  • Socket packages are now always updated to bypass taze's maturity period
  • Ensures teams get the latest Socket packages immediately on every update run

Test plan

  • Run pnpm run update without --apply
  • Verify Socket packages are updated to latest versions
  • All tests pass

The update script was only updating @socketsecurity/* packages when
--apply flag was passed. This meant newly released Socket packages
within taze's 7-day maturity period were being skipped during regular
updates.

Now Socket packages are always updated to bypass the maturity period,
ensuring teams get the latest Socket packages immediately.
@jdalton jdalton enabled auto-merge (squash) January 27, 2026 00:09
@jdalton jdalton merged commit 684abed into main Jan 27, 2026
8 checks passed
@jdalton jdalton deleted the fix/update-socket-packages-always branch January 27, 2026 00:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants