-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separated release and publish CI step #31
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if this will work, have you checked it's working?
eaa77e5
to
8c0073c
Compare
Seems like I managed to fully automate the release process. Updated the PR description accordingly, please check again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hip-hip-hurray! 🙌 The best way to test this is to merge it and release a new version, so let's try it.
Release and update steps were separated into separate pipelines to automate publishing process.
Separated release and publish CI pipeline into two steps:
master
, except forchore(release)
commits done bysemantic-release
Release is now entirely handled by
semantic-release
. New version is calculated, changelog is generated,pubspec.yaml
updated, new version tag is pushed and finally a Github release is created.To trigger the publish pipeline from another Github Action (in this case the release action), the version tag push must be done using PAT (personal access token) of a user, not using the pipeline token. The release pipeline expects
secrets.RELEASE_PAT
to be present.