Repository navigation
chore(beta): refresh from v14.0.0 - #449
Merged
Merged
Conversation
Bring the current v14.0.0 source into beta, including the #448 credential manager refactor (login off http-call) and the main-line catch-up from the recent v14.0.0 rebase (env-derived no-cache flag defaults, dependency bumps). Preserve the published 14.0.0-beta.2 package version, lockfile, beta manifest, and changelog baseline so the next Release Please candidate is 14.0.0-beta.3. No npm release is triggered by this PR.
eablack
force-pushed
the
eb/refresh-beta-from-v14
branch
from
October 20, 2026 18:09
f1c3dbf to
3964571
Compare
The no-cache-default flag test and its oclif-plugin fixture were authored on main under the older lint config and trip v14's stricter rules once rebased in: - fixture: give the eslint-disable directive a description and extend it to cover import-x/no-extraneous-dependencies for the root-resolved @oclif/core. - test: delete the dynamic env key via Reflect.deleteProperty to satisfy @typescript-eslint/no-dynamic-delete. Applied here to unblock the beta release; the same fix is still owed on v14.0.0 in a follow-up PR.
1 task done
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.
Summary
Bring the current
v14.0.0branch source intobetaso the next beta candidate ships the latest v14 work. Replicates the refresh-then-release pattern used for 14.0.0-beta.2 (#440).What this brings into beta on top of
14.0.0-beta.2:@heroku/http-callonto@heroku/heroku-credential-manager(native fetch/undici); removes the oldcredential-manager-core/trees and addscredential-error-reporter.ts.v14.0.0rebase — env-derivedno-cacheflag defaults kept out of generated docs/manifests, plus dependency bumps.The published
14.0.0-beta.2package version, lockfile, beta manifest, andCHANGELOG.mdbaseline are preserved, so the next Release Please candidate is14.0.0-beta.3. No npm release is triggered by this PR.Only four files differ from
v14.0.0:package.json+package-lock.jsonversion pinned back to14.0.0-beta.2, andrelease-please-manifest.beta.json+CHANGELOG.mdrestored frombeta. All other source isv14.0.0verbatim.Type of Change
Patch Updates (patch semver update)
Testing
Notes:
Source is
v14.0.0with only beta version-metadata restored.Steps:
npm run build— passed.npm test— 285 passing.betawithdry_run=trueto verify the beta.3 release PR before any publish.Related Issues
GitHub issue: #N/A
GUS work item: N/A