chore(release): prepare coordinated Ack 1.3.0 release - #141
Merged
Conversation
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.
Summary
Prepare version 1.3.0 for all six ACK packages, including the first
ack_mcp_dartrelease, while preserving compatible dependency minimums and published changelog history.Use Melos 8.7 fixed versions and one workspace tag, compare APIs against 1.2.0, and make publication resumable by checking exact hosted versions before uploading.
Validation and release prerequisite
Full workspace CI under Melos 8.7, release-tag validation, 52 script tests, workflow linting, API compatibility against 1.2.0, and staged publish dry runs for all six packages passed; all seven GitHub checks, including minimum Dart and Flutter SDK checks, passed.
Before pushing
v1.3.0, followPUBLISHING.mdto manually publish the new MCP package from the reviewed release commit and configure its pub.dev OIDC settings, because automated publishing cannot create new packages.