jiayuasu opened a new pull request, #2847: URL: https://github.com/apache/sedona/pull/2847
## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest/community/develop/) ## Is this PR related to a ticket? - No: - this is a documentation update. The PR name follows the format `[DOCS] my subject` ## What changes were proposed in this PR? The 1.9.0 version bump (#2840) updated `python/sedona/version.py` but missed `python/pyproject.toml`, which still declares `version = "1.8.1"`. Since the `[project]` version field is what `setuptools` uses when building the sdist and wheel, publishing as-is would produce `apache_sedona-1.8.1-*.whl` on PyPI even though every other artifact is tagged 1.9.0. This PR: - Bumps `python/pyproject.toml` `[project].version` from `1.8.1` to `1.9.0`. - Updates the release process doc (`docs/community/publish.md`) to prevent this from happening again: - Adds `python/pyproject.toml` to the Python/R/Zeppelin version-update checklist (Step 2), with a warning explaining why this file matters for the PyPI artifact. - Adds a new Step 3 reminding release managers to update `docs/setup/release-notes.md` before cutting a release candidate, since both the vote and announce emails link to it. - Renumbers the downstream sections and the `Failed vote` cross-reference accordingly. ## How was this patch tested? Doc-only and version-string-only change. No code paths are affected. Verified locally: - `python/pyproject.toml` now reports `version = "1.9.0"`. - `docs/community/publish.md` renders correctly with the renumbered sections and updated cross-reference. ## Did this PR include necessary documentation updates? - Yes, I have updated the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
