Release 0.15.1
Release Permifrost
NOTE: Releases should only be initiated by maintainers and owners of the Permifrost project
-
Verify all necessary changes exist on your local master branch (i.e. git pull origin master
) -
Verify that the CHANGELOG.md has correct and up-to-date changes for the release -
Create a bumpversion branch from the master branch (i.e. git checkout -b bumpversion
). Done under !133 (merged) -
From the root of the directory, run make suggest
to determine the recommended version update. Done under !133 (merged) -
Based on the prior step, run make release type=<patch|minor|major>
based on the type of semantic release needed (Optionally, ignore the semantic version if there is concern about the version release recommended bymake suggest
). Done under !133 (merged) -
Push changes to the remote (i.e. git push origin bumpversion
) -
Generate an MR and notify the other maintainers to review the release -
NOTE: For changes required through the review process. Ensure you delete the local tag git tag -d v<x.x.x>
, make the changes, commit and push to GitLab for review
-
-
PyPi Deployment: -
If no changes were required: Upon approval, merge the MR on GitLab and run
git push origin --tags
locally. After CI completes, the new release should now be on PyPi -
If changes were required: Upon approval, merge the MR on GitLab, generate a new tag locally with
git tag -a v<x.x.x> -m "Bump version: <current> -> <update>"
and rungit push origin --tags
. After CI completes, the new release should now be on PyPi
-
If no changes were required: Upon approval, merge the MR on GitLab and run
Announce
-
Send out an announcement in GitLab communications
Message prepared:
great news from the GitLab Data Team.
Happy to announce the release of the new Permifrost version 0.15.1
.
Check the latest version on pypi. Furthermore, if you want to know "what's new" refer to CHANGLOG.md.
Happy 0.15.1
-
Announce in dbt Slack #tools-permifrost channel
Edited by Radovan Bacovic