Update cli-version-checker workflow: add node ecosystem and enforce issue creation #2216
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The CLI version checker workflow had two limitations:
registry.npmjs.orgwas allowed, preventing access to other npm-related domainsSolution
1. Comprehensive NPM Domain Access
Changed network permissions from a single npm domain to the
nodeecosystem identifier:This expands access to all 16 node ecosystem domains including:
npmjs.org,npmjs.com,registry.npmjs.com,registry.npmjs.org,skimdb.npmjs.comnpm.pkg.github.com,yarnpkg.com,get.pnpm.ionodejs.org,bun.sh,deno.landapi.npms.iodeb.nodesource.com,registry.bower.io2. Mandatory Issue Creation
Added explicit requirements in two locations to ensure issues are always created when version changes are detected:
In the Process section:
In the Update Process section:
Testing
Impact
The workflow can now:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.