You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently updated teraslice to use yarn 4, which required changes to the publish pipeline. As part of this update, I added a step to properly configure yarn 4's authentication with the npm token.
In Yarn 1, signing in with the npm CLI was sufficient for running yarn publish. However, with Yarn 4, the new authentication step renders these previous steps redundant. Additionally, echoing GitHub secrets in the pipeline exposes unnecessary risks, even though GitHub protects us from leaking the npm token. We should remove these steps.
I recently updated teraslice to use yarn 4, which required changes to the publish pipeline. As part of this update, I added a step to properly configure yarn 4's authentication with the npm token.
In Yarn 1, signing in with the npm CLI was sufficient for running yarn publish. However, with Yarn 4, the new authentication step renders these previous steps redundant. Additionally, echoing GitHub secrets in the pipeline exposes unnecessary risks, even though GitHub protects us from leaking the npm token. We should remove these steps.
What needs to be removed:
teraslice/.github/workflows/publish-master.yml
Lines 17 to 21 in b36fe30
What's already been added to replace the above code:
teraslice/.github/workflows/publish-master.yml
Lines 44 to 52 in b36fe30
The text was updated successfully, but these errors were encountered: