ci: remove 1.x release workflow

[zepfred]

No description provided.

[Copilot]

Pull request overview

Updates the release-1.x GitHub Actions workflow to improve dispatch UX and add early input validation for community 1.x releases published to Maven Central.

Changes:

• Renamed the workflow for clearer intent (“Release Community 1.x to Maven Central”).
• Made dryRun a typed boolean input and simplified its description.
• Added steps to log workflow inputs and validate the provided release version; also removed unused pull-requests: write permission.

Comments suppressed due to low confidence (1)

.github/workflows/release-1.x.yml:50

• The version validation only checks that the input starts with 1., which still allows shell metacharacters (e.g. 1.0.0$(...)) that could get interpreted later when the version is embedded into shell commands on a self-hosted runner.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

.github/workflows/release-1.x.yml:83

• Unquoted $DRY_RUN allows word-splitting and could inadvertently pass extra Maven arguments if the workflow input contains whitespace; quote it to ensure it is treated as a single boolean value.

[rsynek]

I am a bit confused. Why do we have a 1.x release workflow on both the main branch and the 1.x branch?

I understand we have to have it on the main branch as otherwise, it won't show up in the UI. Why do we need it on 1.x?

[rsynek]

@zepfred since the 1.x release will be only ever started from the main branch, the 1.x workflow is effectively a dead code. Can we rather remove it?

[zepfred]

We cannot delete it from the 1.x branch, or we will not be able to trigger it.