ci: Update android-kit-release action to use the integrations token #62
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
Mansi-mParticle
approved these changes
Jan 24, 2025
Contributor
Mansi-mParticle
left a comment
Mansi-mParticle
left a comment
There was a problem hiding this comment.
Looks good to me
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Summary
mparticle-integrationsorg, theMP_SEMANTIC_RELEASE_BOTtoken is no longer valid and should be removed from the org secrets. All kits should be using the validMP_INTEGRATIONS_SEMANTIC_RELEASE_BOTtoken. This updates the Android kit release action to use that token to fix releases for all Android kits.Testing Plan
Reference Issue