Repository navigation

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

Job	Run time
test-release	15m 18s
test (windows-latest)	18m 16s
e2e-build (macos-latest)	17m 14s
dispatch-tests	16s
release-readiness	9s
test (macos-latest)	17m 14s
node-addon	3m 22s
clippy	56s
lint-ecosystems	27s
hosted-e2e	1m 57s
e2e-build (ubuntu-latest)	3m 44s
e2e-build (windows-latest)	7m 30s
docker-base	6m 15s
coverage	14m 4s
coverage-docker (pypi)	7m 2s
coverage-docker (cargo)	6m 39s
coverage-docker (sbt)	11m 32s
coverage-docker (deno)	4m 36s
coverage-docker (npm)	6m 45s
coverage-docker (gem)	6m 38s
coverage-docker (maven)	5m 45s
coverage-docker (nuget)	6m 38s
coverage-docker (composer)	6m 31s
coverage-docker (golang)	6m 24s
e2e-docker	-1s
e2e	1s
coverage-merge	1s
yarn-berry ${{ matrix.yarn }} (${{ matrix.os }})	1s
e2e-full	1s
cargo old toolchains (manifest [patch])	1s
yarn-berry ${{ matrix.yarn }} (${{ matrix.os }})	1s
yarn-classic ${{ matrix.release }}	1s
cargo ${{ matrix.toolchain }} lock-v${{ (matrix.lock \|\| 'own') }} (${{ matrix.os }})	1s
cargo ${{ matrix.toolchain }} lock-v${{ (matrix.lock \|\| 'own') }} (${{ matrix.os }})	1s
ci-ok	3s
	2h 55m 23s