NEWRELEASE.md

Checklist for new releases

Follow the steps below in order to make a new release in a BikeNetKit repo with package PACKAGENAME.

Preliminaries

• All tested, commited, and merged on main
• Decide on a new version number X.Y.Z using semantic versioning.

Versioning pip

• Create a new releaseX.Y.Z branch
• Update version in PACKAGENAME/_version.py
• Update version in .release-please-manifest.json
• Update version in pyproject.toml
• Update Development Status in pyproject.toml, if needed
• Update version and release date in CITATION.cff
• Update docs/changelog.md . Use gitmojis.
• Update README.md
• Merge, during pull request set Labels > autorelease: tagged
• Check that the new version was updated at https://pypi.org/project/PACKAGENAME/

Versioning Github

• Update last release version in development table of the .github profile README, and Status if needed
• Click Releases
• Draft a new release
• Tag+Release title: Create tag called vX.Y.Z (Target: main)
• Release notes: Copy-paste from changelog.md
• Save draft
• Click Releases: Check draft. Edit. Click Publish release.

Versioning conda forge

• Wait for some hours until the regro-cf-autotick-bot has discovered the new release on PyPI. Once discovered, it may still be queued for several hours here: https://conda-forge.org/status/#version_updates
• Once done, there should be a PR here with the newest release (example growbikenet): https://github.com/pulls/search?q=is%3Aopen+is%3Apr+author%3Aregro-cf-autotick-bot+archived%3Afalse+growbikenet
• If there were no dependency and license changes, and all checks passed: Merge the PR
• If there were dependency or license changes, or not all checks passed: Use the hub tool to push updates/fixes to the branch as needed: https://conda-forge.org/docs/maintainer/updating_pkgs/#pushing-to-regro-cf-autotick-bot-branch
• Once all checks have passed, merge the PR
• Check that the new version was updated at https://anaconda.org/conda-forge/PACKAGENAME (might take a few minutes, also try browser refresh)

Afterwards

• If the docs have new content that relies on the new conda version, wait some hours until it can be installed from conda-forge, then rebuild the docs (without caching). For example, in growbikenet, go to https://github.com/BikeNetKit/GrowBikeNet/actions/workflows/docs_rebuild.yml and "Run workflow".
• If package is in use, run pixi upgrade PACKAGENAME
• Post on LinkedIn
• Post on Mastodon
• Post on Bluesky