Repository navigation

Decide whether a hosted patch is pinned through lockfile discovery alone #2314

Job	Run time
test (windows-latest)	25m 24s
node-addon	3m 1s
clippy	38s
lint-ecosystems	28s
e2e-build (macos-latest)	1h 0m 38s
release-readiness	8s
test (macos-latest)	1h 0m 38s
e2e-build (windows-latest)	6m 21s
docker-base	6m 22s
hosted-e2e	1m 40s
coverage	13m 45s
e2e-build (ubuntu-latest)	3m 44s
test-release	32m 4s
dispatch-tests	17s
coverage-docker (npm)	6m 37s
coverage-docker (pypi)	6m 53s
coverage-docker (sbt)	15m 14s
coverage-docker (cargo)	6m 23s
coverage-docker (composer)	6m 23s
coverage-docker (maven)	7m 5s
coverage-docker (golang)	5m 7s
coverage-docker (gem)	6m 30s
coverage-docker (nuget)	7m 7s
coverage-docker (deno)	6m 24s
e2e-docker	0s
coverage-merge	1m 40s
yarn-berry ${{ matrix.yarn }} (${{ matrix.os }})	1s
yarn-berry ${{ matrix.yarn }} (${{ matrix.os }})	1s
cargo old toolchains (manifest [patch])	1s
yarn-classic ${{ matrix.release }}	1s
cargo ${{ matrix.toolchain }} lock-v${{ (matrix.lock \|\| 'own') }} (${{ matrix.os }})	1s
e2e	1s
e2e-full	1s
cargo ${{ matrix.toolchain }} lock-v${{ (matrix.lock \|\| 'own') }} (${{ matrix.os }})	1s
	4h 50m 39s