Adjust publishing to manual

[skjolber]

No description provided.

[Copilot]

Pull request overview

This PR shifts release publishing from an automatic push-to-main trigger to a manually triggered workflow, and adds a dedicated main-branch verification workflow with Slack notifications.

Changes:

• Added a Verify main workflow that runs Gradle verification on pushes to main and posts success/failure to Slack.
• Updated the main deploy workflow to run via workflow_dispatch with a selectable version increment and tag-based versioning.

Reviewed changes

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

File	Description
.github/workflows/main-verify.yml	New main-branch verification workflow using reusable Gradle verify + Slack notifications.
.github/workflows/deploy-main-manual-gradle.yml	Converts deploy to manual trigger with version increment input; updates publish job and Slack notifications accordingly.

Suppressed comments (2)

.github/workflows/deploy-main-manual-gradle.yml:23

• workflow_dispatch input id contains a hyphen (version-increment), but the expression uses dot notation (inputs.version-increment). In GitHub Actions expressions, keys with hyphens must be accessed with bracket notation (otherwise it can be parsed as subtraction), which will break next_version resolution.
  .github/workflows/deploy-main-manual-gradle.yml:17
• This workflow is now manually triggerable from any ref. Since it publishes to Maven Central and is named "from main", consider enforcing that the publish job only runs on refs/heads/main to prevent accidental releases from feature branches.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.