fix(ci): declare version input on publish-maven

[THEROER]

release.yml's dispatch-downstream runs gh workflow run publish-maven.yml -f version=..., but after the mkdocs retirement publish-maven.yml declared no workflow_dispatch inputs — so the dispatch fails with HTTP 422: Unexpected inputs provided: ["version"], which would break the release chain.

Declare an optional version input (informational only; the published version is still resolved from the checked-out gradle.properties).

Summary by Sourcery

CI:

• Add an optional version input to the publish-maven workflow_dispatch trigger so downstream release automation can pass the version without causing dispatch errors.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the publish-maven GitHub Actions workflow to declare an optional version input on workflow_dispatch so that upstream workflows can pass the version through without causing dispatch errors, while still relying on gradle.properties as the authoritative source of the published version.

Sequence diagram for release.yml dispatching publish-maven with version input

sequenceDiagram
  actor release_workflow
  participant github_actions
  participant publish_maven_workflow

  release_workflow->>github_actions: gh_workflow_run_publish_maven_with_version
  alt before_version_input_declared
    github_actions-->>release_workflow: HTTP_422_unexpected_inputs
  else after_version_input_declared
    github_actions->>publish_maven_workflow: workflow_dispatch_with_version_input
  end

Loading

File-Level Changes

Change	Details	Files
Declare an optional version input for the workflow_dispatch trigger of the publish-maven workflow to restore compatibility with release.yml dispatching and improve traceability.	Extend the workflow_dispatch configuration block to include an inputs section. Add a version input with a descriptive comment explaining it is informational and used for traceability. Configure the version input as non-required with an empty-string default so manual runs remain simple and do not break existing usage.	.github/workflows/publish-maven.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}