Skip to content

fix: exclude non-release modules from Maven deployment - #2481

Merged
zeitlinger merged 1 commit into
mainfrom
fix/release-deploy-reactor
Sep 16, 2026
Merged

zeitlinger merged 1 commit into
mainfrom
fix/release-deploy-reactor

Conversation

@zeitlinger

Copy link
Copy Markdown
Member

Summary

  • Align deployment profiles with the release build, excluding examples, benchmarks, and integration tests.
  • Add CI regression coverage for profile consistency and use the Maven wrapper.
  • Document retrying publication from an unchanged immutable release tag.

Fixes the v1.9.0 deployment failure on example-greeting-service. After merging, dispatch release.yml from main with tag=v1.9.0; no tag change is needed.

Validation

  • mise run lint:fix
  • python3 .mise/tasks/test_release_configuration.py
  • Mutation check: restoring the broken deployment profiles fails the regression test.
  • mise run build-release against current main plus this fix

No publication was triggered. Coverage checks configuration consistency, not signing credentials or Sonatype availability.

Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
@zeitlinger
zeitlinger merged commit f27baf4 into main Sep 16, 2026
17 of 18 checks passed
@zeitlinger
zeitlinger deleted the fix/release-deploy-reactor branch September 16, 2026 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant