Repository navigation
Run the pub.dev publish job in the pub.dev environment - #13
Merged
Merged
Conversation
The re-run of the extensions-v0.8.1 publish got past the tag check (the
pub.dev tag pattern now matches extensions-v{{version}}) and failed on the
next one:
The calling GitHub Action is not allowed to publish, because: publishing
is configured to only be allowed from actions with an environment, this
token originates from an action running in environment 'null'
pub.dev's automated-publishing settings require the `pub.dev` GitHub Actions
environment, and the publish job declared none. pub.dev checks the tag
pattern before the environment, so this requirement was hidden behind the
earlier tag mismatch. The job now declares `environment: pub.dev`; GitHub
creates the environment on the first run that names it.
Header updated to match:
* Lists the environment requirement next to the tag patterns in the one-time
pub.dev setup, and warns that a "protected branches only" deployment rule
on the environment would refuse every tag-triggered run.
* Drops the "if the flutter publish races ahead, re-run it" advice, stale
since auto-tag.yml started waiting for extensions to reach pub.dev before
pushing the extensions_flutter tag.
* Notes that a tag-triggered run uses the workflow as of the tagged commit,
so "Re-run failed jobs" picks up a pub.dev-side fix but never a fix to
this file. That is the case right now: extensions-v0.8.1 points at
adbe895, which has the old workflow, so the tag has to be deleted and
re-created at main (re-running auto-tag.yml does that) after this merges.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K3TbUE73aGPvFr1vqBLQbf
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.
Why
The re-run of the
extensions-v0.8.1publish (run 35653172734, attempt 2) passed the tag check. The pub.dev tag pattern now matchesextensions-v{{version}}. It then failed on the next check:pub.dev's automated-publishing settings require the
pub.devGitHub Actions environment, and the publish job declared none. pub.dev checks the tag pattern before the environment, so the first failure (the tag mismatch) hid this one.What
publish.yml: thepublishjob declaresenvironment: pub.dev. GitHub creates the environment on the first run that names it.auto-tag.ymlwaits forextensionsto reach pub.dev before pushing theextensions_fluttertag.After merging: the tag has to move
extensions-v0.8.1points atadbe895, which still has the old workflow. Re-running that run again will fail the same way. To publish:git push origin :refs/tags/extensions-v0.8.1, or use the repo's Tags page.main. It re-createsextensions-v0.8.1at the newmainusingRELEASE_PAT, which fires this workflow. Once 0.8.1 is live, it pushesextensions_flutter-v0.6.0.extensions_flutterneeds the same pub.dev settings (tag patternextensions_flutter-v{{version}}, environmentpub.dev).Validation
YAML parses and the job carries
environment: pub.devwithid-token: write. Nothing else in the job changed. This can only really be proven by a tag-triggered run, which is step 2 above.🤖 Generated with Claude Code
https://claude.ai/code/session_01K3TbUE73aGPvFr1vqBLQbf
Generated by Claude Code