Repository navigation
ci: Add release workflows - #95
Merged
Merged
Conversation
Adds the same release automation as in the flame repository: - release-prepare.yml: manually triggered, runs melos version and a publish dry run, then opens a release PR. - release-tag.yml: runs on merged release commits on main, creates the package tags and triggers the publish workflow per unpublished package. - release-publish.yml: publishes the package to pub.dev via OIDC and creates a GitHub release from the changelog. Also adds the melos version config from flame and updates the release section in CONTRIBUTING.md. Claude-Session: https://claude.ai/code/session_016h5CfXvZUtr33Nmc4XN8BC
luanpotter
reviewed
Aug 28, 2026
erickzanardo
approved these changes
Aug 28, 2026
luanpotter
reviewed
Aug 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
3 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.
Description
Sets up the same release automation as in flame:
release-prepare.yml: manually triggered (with an optional prerelease flag), runsmelos versionand amelos publishdry run, then opens achore(release): Publish packagesPR.release-tag.yml: runs when a release commit lands onmain, creates the package tags and triggers the publish workflow for each unpublished package.release-publish.yml: publishes the package to pub.dev using OIDC and creates a GitHub release with the notes from the changelog.Also adds the melos
versionconfig from flame (branch: main,releaseUrl,includeCommitId,linkToCommits) and updates the release section inCONTRIBUTING.md.Additionally bumps all GitHub actions to their latest major versions:
actions/checkoutto v7 (was v2/v3/v4),subosito/flutter-actionto v2 (was v1 in the dartdoc job) andamannn/action-semantic-pull-requestto v6 (was v4).Notes
tiledpackage on pub.dev, withflame-engine/tiled.dartand the tag patterntiled-v{{version}}configured.release-prepare.ymlto get CI runs, a PAT or GitHub App token can be passed to thetokeninput ofmelos-action, same as in flame the defaultGITHUB_TOKENis used here.Checklist
docsand added dartdoc comments with///.examplesordocs.Breaking Change?
https://claude.ai/code/session_016h5CfXvZUtr33Nmc4XN8BC