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/ISSUE_TEMPLATE/release-checklist.md
+7-28Lines changed: 7 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,38 +16,17 @@ assignees: ''
16
16
17
17
**Before release**:
18
18
19
-
-[ ] Make sure that all pull requests which will be included in the release have been properly documented as changelog files in the [`changes/` directory](https://github.com/zarr-developers/zarr-python/tree/main/changes).
20
-
-[ ] Run ``towncrier build --version x.y.z`` to create the changelog, and commit the result to `main`.
21
19
-[ ] Check [SPEC 0](https://scientific-python.org/specs/spec-0000/#support-window) to see if the minimum supported version of Python or NumPy needs bumping.
22
-
-[ ] Check to ensure that:
23
-
-[ ] Deprecated workarounds/codes/tests are removed. Run `grep "# TODO" **/*.py` to find all potential TODOs.
24
-
-[ ] All tests pass in the ["Tests" workflow](https://github.com/zarr-developers/zarr-python/actions/workflows/test.yml).
25
-
-[ ] All tests pass in the ["GPU Tests" workflow](https://github.com/zarr-developers/zarr-python/actions/workflows/gpu_test.yml).
26
-
-[ ] All tests pass in the ["Hypothesis" workflow](https://github.com/zarr-developers/zarr-python/actions/workflows/hypothesis.yaml).
27
-
-[ ] Check that downstream libraries work well (maintainers can make executive decisions about whether all checks are required for this release).
28
-
-[ ] numcodecs
29
-
-[ ] Xarray (@jhamman@dcherian@TomNicholas)
30
-
- Zarr's upstream compatibility is tested via the [Upstream Dev CI worklow](https://github.com/pydata/xarray/actions/workflows/upstream-dev-ci.yaml).
31
-
- Click on the most recent workflow and check that the `upstream-dev` job has run and passed. `upstream-dev` is not run on all all workflow runs.
32
-
- Check that the expected version of Zarr-Python was tested using the `Version Info` step of the `upstream-dev` job.
33
-
- If testing on a branch other than `main` is needed, open a PR modifying https://github.com/pydata/xarray/blob/90ee30943aedba66a37856b2332a41264e288c20/ci/install-upstream-wheels.sh#L56 and add the `run-upstream` label.
34
-
-[ ] Titiler.Xarray (@maxrjones)
35
-
-[Modify dependencies](https://github.com/developmentseed/titiler/blob/main/src/titiler/xarray/pyproject.toml) for titiler.xarray.
36
-
- Modify triggers for running [the test workflow](https://github.com/developmentseed/titiler/blob/61549f2de07b20cca8fb991cfcdc89b23e18ad05/.github/workflows/ci.yml#L5-L7).
37
-
- Push the branch to the repository and check for the actions for any failures.
20
+
-[ ] Verify that the latest CI workflows on `main` are passing: [Tests](https://github.com/zarr-developers/zarr-python/actions/workflows/test.yml), [GPU Tests](https://github.com/zarr-developers/zarr-python/actions/workflows/gpu_test.yml), [Hypothesis](https://github.com/zarr-developers/zarr-python/actions/workflows/hypothesis.yaml), [Docs](https://github.com/zarr-developers/zarr-python/actions/workflows/docs.yml), [Lint](https://github.com/zarr-developers/zarr-python/actions/workflows/lint.yml), [Wheels](https://github.com/zarr-developers/zarr-python/actions/workflows/releases.yml).
21
+
-[ ] Run the ["Downstream" workflow](https://github.com/zarr-developers/zarr-python/actions/workflows/downstream.yml) and verify Xarray and numcodecs tests pass.
22
+
-[ ] Run the ["Prepare release" workflow](https://github.com/zarr-developers/zarr-python/actions/workflows/prepare_release.yml) with the target version. This will build the changelog and open a release PR.
23
+
-[ ] Review the release PR and verify the changelog in `docs/release-notes.md` looks correct.
24
+
-[ ] Merge the release PR.
38
25
39
26
**Release**:
40
27
41
-
-[ ] Go to https://github.com/zarr-developers/zarr-python/releases.
42
-
-[ ] Click "Draft a new release".
43
-
-[ ] Choose a version number prefixed with a `v` (e.g. `v0.0.0`). For pre-releases, include the appropriate suffix (e.g. `v0.0.0a1` or `v0.0.0rc2`).
44
-
-[ ] Set the target to `main`.
45
-
-[ ] Set the description of the release to: `See release notes https://zarr.readthedocs.io/en/stable/release-notes.html#release-0-0-0`, replacing the correct version numbers. For pre-release versions, the URL should omit the pre-release suffix, e.g. "a1" or "rc1".
46
-
-[ ] Click on "Generate release notes" to auto-fill the description.
47
-
-[ ] Make a release by clicking the 'Publish Release' button, this will automatically create a tag too.
48
-
-[ ] Verify that release workflows succeeded.
49
-
-[ ] The latest version is correct on [PyPI](https://pypi.org/project/zarr/).
50
-
-[ ] The stable version is correct on [ReadTheDocs](https://zarr.readthedocs.io/en/stable/).
28
+
-[ ][Draft a new GitHub Release](https://github.com/zarr-developers/zarr-python/releases/new) with tag `vX.Y.Z` targeting `main`. Use "Generate release notes" for the description.
29
+
-[ ] Verify the release is published on [PyPI](https://pypi.org/project/zarr/) and [ReadTheDocs](https://zarr.readthedocs.io/en/stable/).
Automated release preparation for v${{ inputs.version }}.
65
+
66
+
This PR was generated by the "Prepare release" workflow. It includes:
67
+
- Rendered changelog via `towncrier build --version ${{ inputs.version }}`
68
+
- Removal of consumed changelog fragments from `changes/`
69
+
70
+
## Checklist
71
+
72
+
- [ ] Review the rendered changelog in `docs/release-notes.md`
73
+
- [ ] Downstream tests pass (see [downstream workflow](https://github.com/zarr-developers/zarr-python/actions/workflows/downstream.yml))
74
+
- [ ] Merge this PR, then [draft a GitHub Release](https://github.com/zarr-developers/zarr-python/releases/new) targeting `${{ inputs.target_branch }}` with tag `v${{ inputs.version }}`
75
+
commit-message: "chore: build changelog for v${{ inputs.version }}"
0 commit comments