Skip to content

chore(bunfig): restore minimumReleaseAge to 604800#5523

Open
waleedlatif1 wants to merge 1 commit into
stagingfrom
bunfig-restore-gate
Open

chore(bunfig): restore minimumReleaseAge to 604800#5523
waleedlatif1 wants to merge 1 commit into
stagingfrom
bunfig-restore-gate

Conversation

@waleedlatif1

Copy link
Copy Markdown
Collaborator

Summary

Type of Change

  • Chore / security config restore

Testing

N/A — one-line config value revert

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Temporarily lowered to 0 in #5521 to get TypeScript 7.0.2 (published
same-day) past the supply-chain safety gate for that merge. Restoring
the 7-day gate now that the merge is done.
@waleedlatif1 waleedlatif1 requested a review from a team as a code owner July 9, 2026 00:04
@vercel

vercel Bot commented Jul 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Error Error Jul 9, 2026 12:04am

Request Review

@cursor

cursor Bot commented Jul 9, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
Single config revert with no app logic impact; slightly stricter install policy than the temporary 0 value.

Overview
Reverts a temporary minimumReleaseAge = 0 in bunfig.toml back to 604800 (seven days), re-enabling Bun's supply-chain install-age check after it was disabled to allow a same-day TypeScript release during a prior merge.

No application code or runtime behavior changes—only install-time dependency policy.

Reviewed by Cursor Bugbot for commit a40fab9. Configure here.

@greptile-apps

greptile-apps Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR restores the Bun install age gate.

  • Sets minimumReleaseAge back to 604800 seconds.
  • Re-enables the 7-day package publication cooldown in bunfig.toml.

Confidence Score: 4/5

Non-frozen Bun install paths can fail while the newly merged TypeScript packages are still inside the 7-day age gate.

  • The changed config restores the intended supply-chain gate.
  • The same line can reject recently published dependencies during developer setup or Docker image builds that re-resolve packages.
  • Frozen CI installs are less exposed, but non-frozen install paths still need a guard or delay.

bunfig.toml

Security Review

The PR restores a supply-chain hardening setting, but the timing can temporarily block valid installs for newly merged packages that are still inside the cooldown window.

Important Files Changed

Filename Overview
bunfig.toml Restores Bun's install age gate to 7 days, which can block non-frozen installs for recently published dependencies.

Reviews (1): Last reviewed commit: "chore(bunfig): restore minimumReleaseAge..." | Re-trigger Greptile

Comment thread bunfig.toml
[install]
exact = true
minimumReleaseAge = 0
minimumReleaseAge = 604800

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 security Install Age Gate Blocks TS7

When this 7-day gate is restored before the newly merged TypeScript 7 packages age out, Bun install paths that re-resolve packages can reject those versions. Developer installs and Docker builds that run bun install without --frozen-lockfile can fail until the package publish times pass the gate window.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

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.

1 participant