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
The `version` field in `python/pyproject.toml` is what `setuptools` uses when building the Python sdist and wheel. If this is not bumped, the PyPI artifact will carry the old version even if `python/sedona/version.py` is correct.
75
+
76
+
## 3. Update release notes
77
+
78
+
Before cutting the release candidate, make sure `docs/setup/release-notes.md` has an entry for {{ sedona_create_release.current_version }} summarizing all changes since the previous release. This file is linked directly from the vote email and the announce email, so it must be in place on the release tag.
79
+
80
+
## 4. Update mkdocs.yml
73
81
74
82
* Please change the following variables in `mkdocs.yml` to the version you want to publish.
75
83
*`sedona_create_release.current_version`
@@ -79,7 +87,7 @@ Make sure the Sedona version in the following files are {{ sedona_create_release
79
87
* Then compile the website by `mkdocs serve`. This will generate the scripts listed on this page in your local browser.
80
88
* You can also publish this website if needed. See the instruction at bottom.
1. In the vote email, say that we will create another release candidate.
579
-
2. Restart from Step 3`Update mkdocs.yml`. Please increment the release candidate ID (e.g., `{{ sedona_create_release.current_version}}-rc2`) and update `sedona_create_release.current_rc` and `sedona_create_release.current_git_tag` in `mkdocs.yml` to generate the script listed on this webpage.
587
+
2. Restart from Step 4`Update mkdocs.yml`. Please increment the release candidate ID (e.g., `{{ sedona_create_release.current_version}}-rc2`) and update `sedona_create_release.current_rc` and `sedona_create_release.current_git_tag` in `mkdocs.yml` to generate the script listed on this webpage.
0 commit comments