Repository navigation
ci: lock the isolated consumer type toolchain - #123
Merged
Merged
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. |
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.
Summary
Install the isolated declaration-checking tools with npm ci against a dedicated lockfile. TypeScript 7.0.2 and @types/node 26.6.3 remain exact. The lock records integrity for all 20 TypeScript platform packages and the same transitive Node type dependency. The constrained-memory image uses the same manifest and lock. Changes to either the project lock or the toolchain lock give CI a new npm download-cache key.
In a replay with equivalent npm caches aged by one day, the previous install revalidated 23 registry metadata entries. With a lockfile, the compiler installed and ran from four cached tarballs with zero registry metadata entries.
Compatibility
The production-only consumer still performs a fresh npm install. The declaration probe still checks the installed compiler and Node types versions and runs with skipLibCheck disabled. The fresh consumer, registry signature checks, release jobs, resource limits and network isolation keep their existing settings.
Verification