Skip to content

Tag 0.1.2 #81

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.

Sign up for GitHub

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

Merged
ilaflott merged 3 commits into from
Apr 16, 2026
Merged

Tag 0.1.2 #81

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
afb2195
Update _version.py
ilaflott Apr 16, 2026
844294e
Update README.md
ilaflott Apr 16, 2026
f027685
Update _version.py
ilaflott Apr 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 12 additions & 7 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -209,11 +209,16 @@ See `CONDA_FORGE_FEEDSTOCK_PLAN.md` for the steps and follow-up tasks to submit

## Releases and Versioning

`fremorizer` has it's own versioning approach/format to avoid confusion with `fre-workflows` and `fre-cli`, which often demand that the version tags match.
the version format is `X.Y.Z`. To publish new release carefully follow the below procedure:
1. create a new branch off of `main`
2. edit the version number in `fremorizer/_version.py` to the desired version tag and open a PR
`fremorizer` uses a post-release scheme to identify development beyond the latest tagged version and tie the current `main` branch to a
`conda` package versioned as `develop`. To avoid confusion with `fre-workflows` and `fre-cli`, which often demand that the version tags
match, `fremorizer`'s version format is `X.Y.Z[.post]`.

### new published release procedure

To publish new release carefully follow the below procedure:
1. create a new branch off of `main`, which is already published to `conda` under `develop`/the previous tagged version + `.post`
2. edit the version number in `fremorizer/_version.py` from the current one, to the desired version tag, remove `.post`, then open a PR. edit nothing else (usually).
3. confirm the branch is functional by letting workflows finish, if you see green checks only, proceed. otherwise, stop and debug.
4. draft a new release pointing to the PR branch, click release. the publishing workflow should trigger and finish.
5. releases in this repository are immutable, **so even if the release workflow fails, breathe and move on to the next step.**
6. edit the version number in `fremorizer/_version.py` to `postX.Y.Z`, and merge the PR assuming all workflow steps passed.
4. draft a new release pointing to the PR branch, click release. the publishing workflow should trigger and finish, and you should see the `X.Y.Z` version in the conda channel.
5. *releases in this repository are immutable*, **so even if the release workflow fails, breathe and move on to the next step.**
6. edit the version number in `fremorizer/_version.py` to `X.Y.Z.post`, and merge the PR to main workflow steps passed. **`publish_conda`** will trigger again and upload what is in `main` under the `conda` version `develop` and `pip` version `X.Y.Z.post`
2 changes: 1 addition & 1 deletion fremorizer/_version.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,5 +3,5 @@
"""

import os
version = os.getenv("GIT_DESCRIBE_TAG", "post0.1.1")
version = os.getenv("GIT_DESCRIBE_TAG", "0.1.2.post")
__version__ = version
Loading