feat(TU-33149): Use an explicit --registry flag for jarvis install#712
Merged
tom-ridsdale merged 1 commit intomainfrom Dec 10, 2025
Merged
feat(TU-33149): Use an explicit --registry flag for jarvis install#712tom-ridsdale merged 1 commit intomainfrom
tom-ridsdale merged 1 commit intomainfrom
Conversation
|
🥷 Code experts: tf-security tf-security has most 👩💻 activity in the files. See details
Activity based on git-commit:
Knowledge based on git-blame: ✨ Comment |
Contributor
Author
|
Sonarcloud issues un-related. |
joycevherck
previously approved these changes
Dec 10, 2025
…ther than a registry override
tom-ridsdale
force-pushed
the
feat/TU-33149
branch
from
134d1d1 to
90ee2bf
Compare
tom-ridsdale
changed the title
|
|
[BOT] Preview available with hash |
promiseNwafor
approved these changes
Dec 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The workflow was setting a global registry override for @Typeform scoped packages:
npm config set @typeform:registry https://npm.pkg.github.com/Idea is that this stayed in effect during the release, causing
semantic-releaseto check authentication against GitHub Packages instead of npmjs.org, resulting in the error.https://typeform.slack.com/archives/C01HXMZGU9E/p1765375968262809?thread_ts=1765366708.689729&cid=C01HXMZGU9E