The upstream driver build script that pinned NODE_VERSION was removed in
microsoft/playwright#41518, so the gitHead lookup only ever led to a 404
and the LTS fallback. The gitHead field is also not available from the
internal npm feed, which failed the release pipeline.
Route all package downloads in the release pipeline through the
DevDiv_PublicPackages Azure Artifacts feed, as required by SFI-ES4.2.4:
- Maven: a pipeline-only settings.xml mirrors central to the feed and
MavenAuthenticate@0 supplies credentials. The published poms and
public CI keep using Maven Central.
- npm: the pipeline writes .npmrc pointing at the feed and runs
npmAuthenticate@0. download_driver.sh now runs npm from the repository
root and uses `npm pack` instead of a hard-coded registry.npmjs.org
URL, so the configured registry is used for both the gitHead lookup
and the playwright-core tarball.
- Skip the release-branch check on manual runs and gate the ESRP publish
job on v1.* tags so the feed setup can be exercised by hand.
Yury Semikhatsky