Skip to content

feat(TU-33149): Use an explicit --registry flag for jarvis install #712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tom-ridsdale merged 1 commit into from
Dec 10, 2025
Merged

feat(TU-33149): Use an explicit --registry flag for jarvis install #712

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,9 +48,7 @@ jobs:
- run: npm config set '//npm.pkg.github.com/:_authToken' $GH_TOKEN
env:
GH_TOKEN: ${{ secrets.GH_TOKEN }}
- run: npm config set @typeform:registry https://npm.pkg.github.com/ # install jarvis from github
- run: yarn add -W @typeform/jarvis
- run: git checkout HEAD -- package.json # do not save jarvis dependency to package.json because it is private (the file is committed by semantic-release to bump version)
- run: npm install @typeform/jarvis --registry=https://npm.pkg.github.com/ --no-save

# authenticate to AWS
- uses: aws-actions/configure-aws-credentials@v4
Expand All @@ -68,7 +66,7 @@ jobs:
AWS_CLOUDFRONT_DIST: 'E3IUO95IYL1RI3'
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
# Hybrid approach: NPM_TOKEN used for verification, OIDC used for actual publishing
# Hybrid approach: NPM_TOKEN for verification, OIDC for publishing
PUBLIC_CDN_URL: 'https://embed.typeform.com'
SEGMENT_WRITE_KEY: ${{ secrets.DEPLOYMENT_SEGMENT_WRITE_KEY }}

Expand Down
Loading