Skip to content

DO NOT MERGE: Validate release-note PR preflight - #2980

Closed
eamsden wants to merge 5 commits into
mainfrom
ea/release-preflight-validation-2973
Closed

DO NOT MERGE: Validate release-note PR preflight#2980
eamsden wants to merge 5 commits into
mainfrom
ea/release-preflight-validation-2973

Conversation

@eamsden

@eamsden eamsden commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Validation only

This draft PR exists solely to exercise the release-note pull-request preflight introduced by #2973. It must not be merged.

The PR workflow has read-only repository permissions and the publication job is push-only, so this run cannot request the protected release environment, access release credentials, publish Maven artifacts, create a tag, or create a GitHub release.

Expected validation:

  • Resolve the synthetic release note with the production metadata script.
  • Generate and validate release-version POM provenance.
  • Build all six native executables.
  • Package archives, permissions, and checksums as Actions artifacts.

This PR will be closed after the preflight completes.

eamsden added 5 commits July 28, 2026 17:05
Replace manual dispatch, Sonatype UI publication, and timed native asset attachment with an approval-gated, retry-safe workflow.
Avoid mixing BSD and GNU stat forms because GNU stat can emit partial filesystem output before the fallback runs.
Drop the mocked release test suite and its per-PR CI job, and move the one-time repository setup out of the workflow README.
Run the production candidate build and packaging path on release-note pull requests without entering the protected release environment. Fix empty-version handling on Bash 3.2 and retry transient Linux native-image Docker builds.
Add a temporary release-note input for a non-publishing workflow run. This branch is for validation only and will not be merged.
@eamsden

eamsden commented Jul 30, 2026

Copy link
Copy Markdown
Contributor Author

Preflight validation passed. The real Prepare release workflow completed metadata resolution, POM provenance validation, all six native builds, packaging, checksum generation, and artifact upload. Publish release was skipped and no protected environment, release credentials, Maven publication, tag, or GitHub release was used. Closing this validation-only PR without merging.

@eamsden eamsden closed this Jul 30, 2026
@eamsden
eamsden deleted the ea/release-preflight-validation-2973 branch July 30, 2026 00:28
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