Fix release pipeline #433
Merged
Fix release pipeline #433
Conversation
This file contains 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
Hopefully this allows pnpm publish (aka npm publish) to properly use the npm token in AUTH_NODE_TOKEN without any additional setup. see npm/cli#1637 see pnpm/pnpm#4937
fussel178
added
🐛 bug
pklaschka
approved these changes
Dec 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR tries to fix the release pipelines for prereleases and releases.
It adds a proper git user to allow the backend-go job tagging and pushing of the required go tag.
(see https://github.com/wuespace/telestion/tree/main/backend-go#releasing-a-new-version)
Additionally, it sets the npm registry in the frontend-react job to hopefully convince npm to use the
NODE_AUTH_TOKEN. 🙈Details
n/a
Additional information
n/a
Related links
CLA
main