ci: use release token for release #791
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
suchapalaver
requested review from
TypeLevelConsoli,
neithanmo and
ryan-s-roberts
auto-merge was automatically disabled
July 23, 2025 11:41
Pull request was converted to draft
Pull Request Test Coverage Report for Build 16476389038Details
💛 - Coveralls |
suchapalaver
force-pushed
the
suchapalaver/ci/use-release-token-for-release
branch
from
49cdb92 to
66698bf
Compare
ryan-s-roberts
approved these changes
Jul 23, 2025
suchapalaver
added a commit
that referenced
this pull request
Jul 24, 2025
This reverts commit f686a5a.
suchapalaver
added a commit
that referenced
this pull request
Jul 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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
RELEASE_TOKENwe were having issues with has been replaced by the goodn people at Edge & Node, so hoping this works!Unfortunately, the proof will be this triggering a release that actually runs its CI checks (the
GITHUB_TOKENwon't do that), 🤞Signed off by Joseph Livesey [email protected]