lucasfang opened a new issue, #507: URL: https://github.com/apache/paimon-cpp/issues/507
### Search before asking - [x] I searched the repository issues for `bump_version` and found no matching issue. ### Paimon-cpp version main at da8818813a85cc6aa20b933b77956c5244109b90 (project version 0.4.0). ### Minimal reproduce step Starting with project/documentation version 0.4.0 and documentation switcher entries `main` and `0.3.0 (stable)`, run the following after publishing 0.4.0: ```bash python3 scripts/releasing/bump_version.py 0.4.0 0.5.0 ``` The script advances CMake and the documentation version to 0.5.0, marks 0.5.0 as stable, and archives 0.3.0. The released 0.4.0 version is missing from the switcher. ### What doesn't meet your expectations? A post-release development bump should mark the old argument (0.4.0, the release just published) as stable while advancing development to 0.5.0. The development entry should remain named `main` with identifier `main` and URL `main/`. The prior stable 0.3.0 should become an archived entry. Stable promotion should also be available independently when no development bump is needed. Both operations should support dry-run and validate metadata before writing. ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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]
