Version 13 is in release-candidate qualification. Pin the exact approved candidate and review its package changelog; a release candidate is not a stable-release recommendation. Keep the framework and browser SDK versions aligned and preserve your existing service name, consent settings and tracing owner.
Installing a newly published version
A successful publish does not mean a customer’s package manager will accept the version immediately. A seven-day policy makes a version published at time D eligible at D + 7 days; a fourteen-day policy makes it eligible at D + 14 days. Check every newly resolved dependency: the latest eligibility time governs the install. Publishing stable starts a new clock; time spent qualifying an RC does not age the stable package.
For an authorized preview before that date, record the exception in the upgrade PR. Prefer exclusions for the reviewed packages, including new transitive packages such as @interfere/javascript and @interfere/build. Pin the approved versions and inspect the lockfile diff. An exception to the age policy is not release qualification or permission to deploy.
pnpm
In pnpm-workspace.yaml, retain existing exclusions and add the Interfere packages used by the app. pnpm measures minimumReleaseAge in minutes; 10080 is seven days.
1minimumReleaseAge: 100802minimumReleaseAgeExclude:3 - "@interfere/*"
The scope pattern covers fresh transitive Interfere dependencies too, but exempts future versions as well. Use explicit package entries if your policy requires a narrower exception. Merge this example into the existing list rather than replacing it. Update the lockfile with pnpm install --no-frozen-lockfile, then verify pnpm install --frozen-lockfile with the committed policy.
For a one-off approved local resolution instead of a persistent exclusion:
1pnpm install --no-frozen-lockfile --config.minimumReleaseAge=0That command relaxes the age gate for the entire resolution. Review all changed dependencies, restore the normal policy and verify the resulting frozen install in CI; do not assume a local override applies to CI. See pnpm’s release-age settings.
Bun
Bun measures install.minimumReleaseAge in seconds; 1209600 is fourteen days. Merge the packages present in your dependency graph into the existing exclusions in bunfig.toml:
1[install]2minimumReleaseAge = 12096003minimumReleaseAgeExcludes = ["@interfere/next", "@interfere/react", "@interfere/javascript", "@interfere/build", "@interfere/types", "@interfere/constants", "@interfere/helpers"]
Include @interfere/vite when used and any other newly resolved Interfere package reported by the installer. Preserve existing exclusions. If frozenLockfile = true, temporarily set it to false while regenerating the lockfile, then restore it before committing. A one-off approved alternative is bun install --minimum-release-age=0 during that regeneration; this bypass applies to the entire resolution. Review the diff and run bun install --frozen-lockfile with the restored policy. See Bun’s install settings.
What an upgrade recommendation must say
Record the affected versions and configuration, the verified impact or requested feature, the exact target version, and whether action is required or optional. Include the package manager and version, release-age threshold, package publication times, earliest install time without an exception, chosen exclusion or one-off override, lockfile regeneration command, and frozen-install CI evidence. Keep the upgrade limited to SDK packages and their required lockfile changes.
Customer canary evidence must name the exact candidate and the approved release-age exception. A day-seven stable decision cannot assume a fresh stable version is installable that day. If an exception is not approved, schedule installation after the customer’s threshold and leave the preview evidence pending.