You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: .github/release_workflow.md
+4-1
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ This file contains the workflow required to make a `PyBaMM` release on GitHub, P
9
9
-`pybamm/version.py`
10
10
-`docs/conf.py`
11
11
-`CITATION.cff`
12
+
-`pyproject.toml`
12
13
-`vcpkg.json`
13
14
-`docs/_static/versions.json`
14
15
-`CHANGELOG.md`
@@ -32,6 +33,7 @@ If a new release candidate is required after the release of `rc0` -
32
33
-`pybamm/version.py`
33
34
-`docs/conf.py`
34
35
-`CITATION.cff`
36
+
-`pyproject.toml`
35
37
-`vcpkg.json`
36
38
-`docs/_static/versions.json`
37
39
-`CHANGELOG.md`
@@ -53,6 +55,7 @@ Once satisfied with the release candidates -
53
55
-`pybamm/version.py`
54
56
-`docs/conf.py`
55
57
-`CITATION.cff`
58
+
-`pyproject.toml`
56
59
-`vcpkg.json`
57
60
-`docs/_static/versions.json`
58
61
-`CHANGELOG.md`
@@ -70,7 +73,7 @@ Once satisfied with the release candidates -
70
73
Some other essential things to check throughout the release process -
71
74
72
75
- If updating our custom vcpkg registory entries [pybamm-team/sundials-vcpkg-registry](https://github.com/pybamm-team/sundials-vcpkg-registry) or [pybamm-team/casadi-vcpkg-registry](https://github.com/pybamm-team/casadi-vcpkg-registry) (used to build Windows wheels), make sure to update the baseline of the registories in vcpkg-configuration.json to the latest commit id.
73
-
- Update jax and jaxlib to the latest version in `pybamm.util` and `setup.py`, fixing any bugs that arise
76
+
- Update jax and jaxlib to the latest version in `pybamm.util` and `pyproject.toml`, fixing any bugs that arise
74
77
- Make sure the URLs in `docs/_static/versions.json` are valid
75
78
- As the release workflow is initiated by the `release` event, it's important to note that the default `GITHUB_REF` used by `actions/checkout` during the checkout process will correspond to the tag created during the release process. Consequently, the workflows will consistently build PyBaMM based on the commit associated with this tag. Should new commits be introduced to the `vYY.MM` branch, such as those addressing build issues, it becomes necessary to manually update this tag to point to the most recent commit -
0 commit comments