Repository navigation
Backport bounded minimatch expansion without changing the matcher API - #2
Conversation
|
The inherited upstream PR workflows queued over a thousand platform-matrix jobs and were canceled to free capacity for current development checks. This includes the generic e2e run that had started. Those canceled runs are not passing evidence. The inherited CodeQL workflow separately ended with The dedicated matcher source owner remains active on the exact PR source with only its diagnostic workflow added. It will check the locked install, both source verifiers, rebuilt runtime bundles, upstream tests and source-refusal controls, and retain the selected build evidence. |
|
The focused Linux owner passed on the exact candidate source with only its diagnostic workflow added: locked install, source verifiers, both bundle rebuild comparisons, 11 suites / 249 tests and the two matcher source controls passed. Artifact 13406518961 has SHA-256 The inherited CodeQL workflow reported startup failure before creating any job or log, so its cause is not established and it is not a pass. Inherited platform matrix copies were canceled to prioritize the focused owner and current development checks. Downstream scanner integration remains separate. |
The setup-python action uses
@actions/glob, which calls the minimatch 10matchOneAPI. Upgrading that dependency to minimatch 11 breaks recursive matching. Retain minimatch 10.2.5 and apply the reviewed upstream expansion-bound fix to its CommonJS and ESM entry points, then rebuild the action bundles.The deterministic source archive preserves the upstream package identity, dependency graph, license and unchanged files. An installed-source verifier checks the original and repaired archives, recipe, owner and lock identities, every v10 lock copy, package metadata, license and both installed source postimages before the build. Focused tests cover expansion bounds, the existing
matchOneAPI, and refusal of duplicate lock entries or changed source/archive bytes. Upstream minimatch 10.2.5 is still an affected release; this is a maintained source repair, not a new upstream release or an advisory exception.On Windows with Node 24.19.0/npm 11.17.0, clean locked installation, npm ls, the existing deepmerge verifier, both action rebuilds and all 11 Jest suites / 249 tests passed. Fifteen real
@actions/globpattern scenarios matched the original action, and the two focused source tests passed. Linux hosted build and downstream independent scanner qualification are pending.