Fix publish workflow failing on the flutter_webrtc pin warning - #1140
Open
hiroshihorie wants to merge 2 commits into
Open
Fix publish workflow failing on the flutter_webrtc pin warning#1140hiroshihorie wants to merge 2 commits into
hiroshihorie wants to merge 2 commits into
Conversation
hiroshihorie
requested review from
cloudwebrtc and
xianshijing-lk
as code owners
July 28, 2026 09:14
|
Warning No changeset found If this PR includes user-facing changes, please add a changeset file in Format: |
cloudwebrtc
approved these changes
Jul 28, 2026
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
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.
Every publish workflow run in this repo's history has failed with exit code 65. The dart-lang reusable publish workflow runs a non-interactive
dart pub publish, which treats any validation warning as fatal. Our exactflutter_webrtcpin is intentional (the native WebRTC-SDK pods must match between the two packages) but always produces the 'should allow more than one version' warning, so the workflow can never succeed and every release so far has been published manually.This replaces the reusable workflow with an inline job that publishes with
--force, which downgrades warnings to informational.dart-lang/setup-dartis kept solely for pub.dev auth: withid-token: writeit mints a temporary pub.dev token from the GitHub OIDC token and registers it in the shared pub config, which the Flutter-sidedart pub publishthen picks up. The pub.dev trust configuration is based on repository and tag claims, not the workflow definition, so no changes are needed on the pub.dev side.