ci: migrate versioning from standard-version to mtrust-api-guard - #4
Merged
Conversation
- Replace standard-version (Node.js) with mtrust_api_guard version command - Use GitHub App (bumper bot) token instead of ELEVATED_TOKEN PAT for release commits/tags, enabling tag-push-triggered pub.dev workflows - Downgrade runners from macos-latest to ubuntu-latest for version jobs - Add [skip ci] guard to prevent workflow loops on version bump commits - Add api_changes job to PR workflows (pr_dev, pr_main) for API diff visibility — posts next version + changelog to PR comments - Add api_guard entry_points config to analysis_options.yaml - Regenerate CHANGELOG.md from API diffs across all existing git tags - Remove package.json / standard-version / commitizen tooling
Merge duplicate build_dev and build_main version jobs into a single reusable workflow (build_workflow.yaml). Callers pass branch and pre_release as inputs; the workflow handles the rest. - build_dev.yaml: delegates with branch=dev, pre_release=true - build_main.yaml: delegates with branch=main, pre_release=false - rebase_dev job runs conditionally when branch == main
Version AnalysisNext Version: Changelog: 📄 View detailed changelog in job summary Badge: |
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
Replaces the Node.js-based
standard-versionversioning pipeline with mtrust-api-guard — an API-diff-driven semver tool built for Dart/Flutter packages.Changes
Workflows
build_dev.yaml/build_main.yaml: Replacestandard-version+update-pubspecaction chain withmtrust_api_guard version. Switched fromELEVATED_TOKENPAT to the bumper GitHub App token (BUMPER_APP_ID/BUMPER_APP_KEY) so tag pushes correctly trigger downstream pub.dev publish workflows. Runners downgraded frommacos-latest→ubuntu-latest.[skip ci]guard added to prevent workflow loops on version bump commits.pr_dev.yaml/pr_main.yaml: Addedapi_changesjob — dry-runs api-guard (--no-commit --no-tag) and posts the predicted next version + changelog as a PR comment.Config
analysis_options.yaml: Addedapi_guard.entry_pointspointing atlib/mtrust_barcode_kit.dart.Cleanup
package.json: Removed —standard-version,commitizen, anddart_version.jsare no longer needed.CHANGELOG.md: Fully regenerated from actual API diffs across all existing git tags usingmtrust_api_guard changelog --regenerate.Pre-release format
Pre-release versions retain the existing
2.1.0-0style (via--pre-release-prefix ""), so thepublish_dev.yamltag trigger pattern (v[0-9]+.[0-9]+.[0-9]+-[0-9]+) requires no changes.