ci: pub.dev publishing via GitHub Actions (OIDC)#22
Open
terra-alex wants to merge 2 commits into
Open
Conversation
…OS ~> 1.7.9, terra-android 1.7.1)
No token/secret — uses pub.dev automated publishing (OIDC). Push a v<version> tag to release. Requires enabling Automated publishing on pub.dev for this repo.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds CI publishing for terra_flutter_bridge — pushing a
v<version>tag publishes to pub.dev via GitHub Actions OIDC (no token/secret to manage).Setup required on pub.dev (one-time, by a publisher admin): package Admin → Automated publishing → Enable publishing from GitHub Actions, set repository
tryterra/terra-flutterand tag patternv{{version}}. After that, release by taggingvX.Y.Zonmain(matching the pubspec version).