amaechler opened a new pull request, #20694: URL: https://github.com/apache/druid/pull/20694
### Description `get_milestone_number` in `.github/scripts/auto-add-milestone.sh` returns the milestone number on stdout. When the milestone does not exist yet, it also echoes `Creating milestone: <title>` to stdout, so the caller sends both lines as the milestone and GitHub rejects the update with HTTP 422. The first PR merged for each new version therefore gets no milestone. The [PR Merged run](https://github.com/apache/druid/actions/runs/39285167259) for #20625, which moved `master` to `40.0.0`, failed this way on 2026-10-19 with `"value":"Creating milestone: 40.0.0\n70"`, and #20625 still has no milestone. The run for the `39.0.0` version bump also failed; its logs are no longer available, but I suspect the same cause. This PR prints the message to stderr, so it still shows up in the job log. #### Testing I ran the script before and after the change against a stub `gh` with no existing milestone. Before, the update was sent with `milestone=Creating milestone: 41.0.0` and `77` on the next line, and failed. After, it was sent with `milestone=77` and succeeded, and `Creating milestone: 41.0.0` still appeared in the output. The same 422 also showed up in an end-to-end run of the workflows from #20693 in a scratch repository. <hr> This PR has: - [x] been self-reviewed. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
