Skip to content

chore: migrate to changeset-based release process - #289

Merged
marandaneto merged 6 commits into
mainfrom
feat/changeset-release-process
Feb 19, 2026
Merged

marandaneto merged 6 commits into
mainfrom
feat/changeset-release-process

Conversation

@marandaneto

@marandaneto marandaneto commented Feb 18, 2026 •

Copy link
Copy Markdown
Member

💡 Motivation and Context

follow up #230
#skip-changelog

Screenshot 2026-02-18 at 17 50 32

💚 How did you test it?

will do once merged so i can test all the configs

📝 Checklist

  • I reviewed the submitted code.
  • I added tests to verify the changes.
  • I updated the docs if needed.
  • No breaking change or entry added to the changelog.

- Replace tag-based publish workflow with changeset-driven release workflow
- Add @changesets/cli for version management (via pnpm)
- Add .github/actions/setup composite action for Flutter + Node.js
- Add Slack notifications, approval gates, and GitHub release creation
- Publish to pub.dev via OIDC authentication
- Update RELEASING.md with new process
- Remove prepare-release.sh (replaced by changesets)
@marandaneto
marandaneto requested a review from a team as a code owner February 18, 2026 16:36
Comment thread .github/workflows/publish.yml Dismissed
Comment thread .github/workflows/publish.yml Dismissed
Comment thread .github/workflows/publish.yml Dismissed
Comment thread .github/workflows/publish.yml Dismissed
Comment thread .github/workflows/publish.yml Dismissed
run: |
git tag -a "${{ steps.get-version.outputs.committed-version }}" -m "${{ steps.get-version.outputs.committed-version }}"

- name: Publish to pub.dev

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread .github/workflows/publish.yml Outdated
runs-on: ubuntu-latest
# Use `always()` to ensure the job runs even if the notify-approval-needed job fails
if: always() && needs.check-changesets.outputs.has-changesets == 'true'
environment: 'pub-Release' # Requires approval from a maintainer

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines +105 to +114
- name: Apply changesets and update version
id: apply-changesets
run: |
pnpm changeset version
NEW_VERSION=$(node -p "require('./package.json').version")
echo "new-version=$NEW_VERSION" >> "$GITHUB_OUTPUT"
echo "New version: $NEW_VERSION"

- name: Sync version to all platform files
run: ./scripts/bump-version.sh ${{ steps.apply-changesets.outputs.new-version }}

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i dont like this version dance but theres no similar changeset package for pub, or not something that is up to date

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why dont you contribute to github.com/bruits/sampo? I did it for php and python and I'm migrating those two repos this very week. In an ideal world the client libraries team would continue that work going and just reuse sampo. It's a great tool!

@marandaneto marandaneto Feb 18, 2026 •

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1st we get this going across all repos then we polish the ones that aren't supported yet with sampo or else pinky promise

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm happy with that!

@marandaneto
marandaneto enabled auto-merge (squash) February 19, 2026 09:24
@marandaneto
marandaneto merged commit 8b03e44 into main Feb 19, 2026
16 checks passed
@marandaneto
marandaneto deleted the feat/changeset-release-process branch February 19, 2026 09:33
@marandaneto marandaneto mentioned this pull request Feb 19, 2026
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants