ci: add frozen pnpm install check#9
Open
vorflux[bot] wants to merge 1 commit into
Open
Conversation
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.
Adds an install-only dependency-integrity check for PNPM and removes unnecessary dependency lifecycle-script trust. The workflow verifies that the committed lockfile installs reproducibly without exposing credentials or running package install hooks.
Changes
pnpm install --frozen-lockfilefor pull requests into and pushes todevelop, using pinned Node.js 24.18.0 and PNPM 10.34.5 with lockfile-keyed PNPM store caching.@firebase/util,esbuild,protobufjs,sharp, andunrs-resolver.Testing
pnpm install --frozen-lockfile --reporter ndjsonpnpm:lifecycleevents.actionlint .github/workflows/ci.yml<isolated-workspace>ResolverFactoryoperation.<isolated-run-root>origin/developSHA-256:a51e86240e834ce51afc04ecb0367cbc526e1fd23c6ef52be4ca1b1bc2e759aa.git diff --checkand final two-file scope review.pnpm auditreported 69 pre-existing findings: 6 low, 28 moderate, 32 high, and 3 critical. These require urgent dependency-remediation follow-up and are not represented as passing.next lintis invalid on Next.js 16;next buildrequiresFIRESTORE_CONFIGduring page-data collection. None is represented as passing.Test evidence:
Attached Images
[run_consumer_probes.sh]
[verify_lockfile.sh]
[REPORT.md]
View in Vorflux Session
Session Details
(aside)to your comment to have me ignore it.