Skip to content

chore(yarn): ensure network isolation for the build and tests#676

Merged
pavelglac merged 51 commits into
mainfrom
pavelglac/ado-pipeline-npm-mirror-registry
Jul 14, 2026
Merged

chore(yarn): ensure network isolation for the build and tests#676
pavelglac merged 51 commits into
mainfrom
pavelglac/ado-pipeline-npm-mirror-registry

Conversation

@pavelglac

@pavelglac pavelglac commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Why

Upgrade to yarn4 and ensure network isolation for the install, build and tests. For now there is not network isolation for the npm release (for the internal release there is). This will be addressed by bumping beachball and change the release pipeline according to microsoft/beachball#1281

Pavel Glac and others added 29 commits June 17, 2026 10:56
Configure yarn install steps to use the internal npm mirror
(https://domoreexp.pkgs.visualstudio.com/_packaging/npm-mirror/npm/registry/)
instead of the public npm registry.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Replace inline .npmrc generation with checked-in config files
for npm mirror and ADO feed, and wire pipeline steps to use them
via NPM_CONFIG_USERCONFIG.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
npmAuthenticate@0 requires authenticating a valid .npmrc path.
Move checked-in configs to .npmrc filenames under dedicated folders
and update workingFile and NPM_CONFIG_USERCONFIG references.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@pavelglac pavelglac force-pushed the pavelglac/ado-pipeline-npm-mirror-registry branch from fd18179 to b962048 Compare June 19, 2026 08:56
@pavelglac pavelglac changed the title Use ADO npm mirror for release pipeline installs bump yarn, ensure network isolation for the build and tests Jun 19, 2026
@pavelglac pavelglac changed the title bump yarn, ensure network isolation for the build and tests chore(yarn): ensure network isolation for the build and tests Jun 19, 2026
@microsoft microsoft deleted a comment from github-actions Bot Jun 22, 2026
@github-actions

Copy link
Copy Markdown

📊 Benchmark Analysis Report

No significant performance changes detected


Threshold: 5% change


Updated: 2026-06-22T15:08:34.078Z

git config user.email "gql-svc@microsoft.com"
git config user.name "Graphitation Service Account"
git fetch --depth=2
git fetch origin main

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you sure you don't want to keep depth for faster checkout? fetching all history looks like overkill here

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Without it I was getting: fatal: shallow file has changed since we read it. For performance I would not be bothered.

image


parameters:
# settings:
# networkIsolationPolicy: Permissive,CFSClean

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should it be commeneted?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, currently our pipeline cannot run in network isolation because of npmjs and github enpoints during the release.

@pavelglac pavelglac merged commit fa8602c into main Jul 14, 2026
10 checks passed
@pavelglac pavelglac deleted the pavelglac/ado-pipeline-npm-mirror-registry branch July 14, 2026 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants