Repository navigation
feat(release): automate pub.dev publishing and repository templates - #46
Merged
Merged
Conversation
ProjectAJ14
marked this pull request as ready for review
September 21, 2026 23:07
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.
Merges to
mainwill use the pinned Melos 8 workspace to version changed public packages and affected dependents, validate them, and push one release commit plus individual package tags. Each tag publishes through pub.dev OIDC using thepub.devenvironment. Failed preparation or publication runs create a deduplicated GitHub issue with diagnostics and recovery links.The release CLI supports dry runs and partial-release recovery, waits for dependencies to reach pub.dev, and skips already-published versions. Version hooks stage their output into the single release commit and propagate failures. Publishing resolves each package independently of the local Dart workspace.
Adds bug/feature issue forms, a PR template, contribution/security/conduct guidance, Dependabot configuration, and a step-by-step authentication and recovery guide in
docs/RELEASING.md.Validation: 23 Node tests pass, including real Melos 8 versioning of a changed package and its dependent; the four release workflows pass actionlint; workspace formatting and analysis pass; root Dart tooling passes with 102/102 executable lines covered. Real isolated-package resolution, analysis, tests, and
pub publish --dry-runpass for cli_core and timer_button with zero publish warnings.Activation setup is complete: all 11 pub.dev package publishing policies are saved and verified for package-specific tags, push events, and the
pub.devenvironment. The release App private-key secret is stored and verified; all PR checks pass. The App is installed only on this repository; its App ID, environment tag policy, branch bypass, and immutable release-tag rules are configured. Merging activates the pipeline and can release accumulated versionable changes since existing package tags.