Repository navigation
Conversation
This branch has not been deployed
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
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.
Problem
For bun-global providers (OpenCode v2,
@opencode/cli), T3 Code advertises npm'slatestdist-tag. bun's[install] minimumReleaseAgerefuses releases newer than the limit, sobun i -g pkg@latestinstalls the newest older release instead. T3 then shows "Update command completed, but T3 Code still detects an outdated provider version." and keeps offering the same update until the release ages past the limit.Repro:
minimumReleaseAge = 604800in~/.bunfig.toml, OpenCode installed at 2.2.0, npmlatestat 2.2.5 (published 2026-10-30).bun add @opencode/cli@latestinstalls 2.2.0 and exits 0. An exact pin to 2.2.4 fails withblocked by minimum-release-age. Details are in #30632.Change
~/.bunfig.tomlsets[install] minimumReleaseAgeand the package is not inminimumReleaseAgeExcludes, the bun-global latest lookup returns the newest stable version whose npm publish time is at least that old. The advertised version now matches what@latestinstalls.bun i -g <pkg>@latest. Pinning the version would fail for versions bun refuses, so it is not used.npmis missing, the time lookup fails, or no version is eligible, the lookup returnsnulland the existing npmlatestbehavior applies.parseBunReleaseAgeConfigandselectReleaseAgeEligibleVersionare exported and unit-tested.Only bun-global installs change. npm-global is handled by #24062. pnpm is handled by #19580. Vite+ global installs are not covered.
Scope and approval
Triage issue: #30632. It is awaiting maintainer triage, so this PR is a draft until the issue is triaged. This is the bun counterpart of the npm and pnpm policy in #15329 and #19580: T3 advertises only the version the package manager running the update will install. #21422 and #14249 are the related closed issues.
Verification
maintenanceResolver.ts: bunfig parsing ([install]vs[run]scoping, comments, excludes, no-setting case) and eligible-version selection (prerelease anddevtags skipped,created/modifiedkeys ignored, cutoff boundary, all-too-new returns null). Passed.@opencode/cliwith bun 1.3.3 underminimumReleaseAge = 604800:@latestinstalled 2.2.0. The helper selects 2.2.0 from the same publish times.vp test/ vitest formaintenanceResolver.test.ts, typecheck, and lint.pnpm install --frozen-lockfilefailed in my environment withERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION(@effect/sql-d1@4.1.1, inside the local 7-day policy). The repo's tests need to run in CI or a clean checkout.bun i -gupdate through the T3 UI.