Release procedure
This a quick checklist to run through when we’re preparing for a new release.
Core dependencies
The following packages must be updated to the same version as Lookyloo.
For example, if the lookyloo release is v1.8.0
their version must be v1.8.X
.
The last digit will mainly be used for bug and security fixes, but it might also be
used for new features.
Bump versions
Across all the packages, bumping version means the following:
-
Edit
pyproject.toml
, keyversion
to the version you want. Example:1.8.0
. -
Edit
setup.py
, keyversion
to the next development version. Example:1.9-dev
. -
Run
poetry update
to update all the dependencies. -
Commit and push.
-
Wait for the continuous integration to finish, fix the code if needed.
-
Tag and sign the last commit. Example:
git tag -s v1.8.0
. -
Push the tags with
git push --tags
.
Lookyloo
The release process will be very similar to the core dependencies, but with a few additions
Bump version
-
Edit
pyproject.toml
:-
Bump the key
version
to the version you want. Example:1.8.0
. -
Bump the required version of the core dependencies to the new release. Example:
^1.8
.
-
-
Edit
setup.py
, keyversion
to the next development version. Example:1.9-dev
. -
Run
poetry update
to update all the dependencies.-
Note: The packages for the core dependencies may not be available immediately, if you see an error, go get a glass of water and try again in 5 min.
-
-
Update the 3rd party dependencies used in the website:
-
Check the latest release of DataTables
-
Check the latest release of D3.js
-
If needed, update
tools/3rdparty.py
accordingly -
Run
tools/3rdparty.py
-
Run
tools/generate_sri.py
-
Make sure to restart and check if the website is still working as it should.
-
-
Commit and push.
-
Wait for the continuous integration to finish, fix the code if needed.
-
Tag and sign the last commit. Example:
git tag -s v1.8.0
. -
Push the tags with
git push --tags
.