paleolimbot opened a new issue, #134: URL: https://github.com/apache/sedona-db/issues/134
I forgot to put this in the release instructions, but the nightly Python packages rely on a tag to version themselves after a release: https://github.com/apache/sedona-db/blob/aa6c8ea5d10dbfaec2216ecf7f7c35c71a3afa57/ci/scripts/set_dev_version.py#L60-L62 Currently this is getting calculated as `0.1.0-alpha287`, which is not really the end of the world, but in theory we'd like the dev versions to have a version number greater than `0.1.0`. https://github.com/apache/sedona-db/actions/runs/17937024971/job/51004986580#step:7:20 I think creating the tag `apache-sedona-db-0.2.0.dev` and pushing it upstream after the version update PR merges should do it. -- 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]
