[venkata-kishore]

The release check looked only at the root artifact. In a multi-module release, GitHub Packages receives modules one at a time, so a deploy that stopped partway left some modules there and not others. A retry then saw the root, decided GitHub Packages was done, and skipped the rest.

What changes in maven-release.yml

• Module list. The check step reads the effective POM with the publish profile (help:effective-pom) and lists every module.
• Skips honoured. A module stays out of a registry's check through the same properties the build uses: maven.deploy.skip for GitHub Packages, skipPublishing for Central.
• Each module checked. Central through its pom URL on repo1, GitHub Packages through the org packages versions API, the same calls as before.
• Outcome per registry.
  • Every module present: "already on ..., skipping that upload", as before.
  • None present: upload.
  • Some present: the run stops with an error naming which modules have the version and which do not.
    • GitHub Packages: delete that version from the packages that have it, then re-run.
    • Central: one upload carries every module, but they can reach repo1 at different times, so the error says to check the deployment in the Central Portal and re-run once it is published.
• Unchanged. Single-module libraries get the same result as before. The artifact output is still the root's.

Tested

• Stubbed registries. The step's script was extracted from the workflow and run against a five-module reactor with three published modules and one unpublished test module.
  • Nothing published: both uploads run.
  • Everything published: both skipped.
  • GitHub partial: error.
  • Central partial: error.
  • Central complete, GitHub empty: only the GitHub upload runs.
  • A module with skipPublishing: it is left out of the Central check only.
  • A 503 from the registry: error.
  • The unpublished test module was never queried.
• Live registries, read-only. On bonfire-oss-parent at v2.1.1, the script reports the tag, Central and GitHub Packages as already done, with exit 0.

actionlint was not run.