ci: use correct github token #386
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
HayesGordon
commented
Nov 5, 2025
| @@ -1,75 +0,0 @@ | |||
| name: Publish Rive React Native pre-release | |||
Contributor
Author
There was a problem hiding this comment.
This pre-release was me experimenting a while ago. Can be deleted
umberto-sonnino
approved these changes
Nov 5, 2025
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.
Recent changes to restrict directly pushing to main broke the release action - which we've been manually patching after each release. Initially, there were some missing auth config in settings for this repository which we thought was the issue.
But looks like React Native is still using an old key that no longer exists.
This is all that I noted that is different between our CI in WASM compared to React Native.