- personal github token: store it in the file
token
- Add the package name to the
packageslist inrelease_info.py - Add the package name (without a version pin) to the
dependencieslist in../pyproject.toml - Add the package name to the appropriate
federation_hierarchylayer in../pysal/base.py - Add the package name to the
submoduleslist in the corresponding layer__init__.py(e.g.../pysal/model/__init__.py) - Create a proxy module
../pysal/<layer>/<package>/__init__.pywithfrom <package> import * - Add the package to all CI environment files in
../ci/
- Remove the package name from the
packageslist inrelease_info.py - Remove the package from the
dependencieslist in../pyproject.toml - Remove the package from
federation_hierarchyin../pysal/base.py - Remove the package from the
submoduleslist in the corresponding layer__init__.py - Delete the proxy module directory
../pysal/<layer>/<package>/ - Remove the package from all CI environment files in
../ci/
-
Update relevant data on
start_date(day after last release),release_date(day of this release),version, anduserinrelease.yamlIf this is a release candidate, do not start the
versionstring withvbut do addrcXad the end of the string, whereXis the number for the current release candidate.If this a production release, the first character in
versionneeds to bvto ensure the publish and release workflow is run in the CI.
makewill run all the steps required to build the new change log
For debugging purposes, the individual steps can be run using:
make frozenwill get information about latest package releasesmake gitcountwill get issues and pulls closed for each packagemake changelogwill update the change log and write tochanges.md
These require release_info.py
git add ../pyproject.tomlgit add release.yamlgit commit -m "REL: <version>"
git tag <version>git push upstream <version>
- edit the file
changelog.mdand incorporate into the release notes on github