fix ncipollo/release-action not being able to write #2545
Merged
Conversation
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
MatteoPologruto
approved these changes
Feb 19, 2024
per1234
added
topic: infrastructure
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.
ncipollo/release-action#208 (comment)
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
- [ ] Tests for the changes have been added (for bug fixes / features)- [ ] Docs have been added / updated (for bug fixes / features)- [ ]UPGRADING.mdhas been updated with a migration guide (for breaking changes)- [ ]configuration.schema.jsonupdated if new parameters are added.What kind of change does this PR introduce?
Bug fix
What is the current behavior?
After #2541 the release CI is not working anymore:
What is the new behavior?
The release pipeline should be able to push again the artifacts on the github releases
Does this PR introduce a breaking change, and is titled accordingly?
no
Other information