Skip to content

Add release gates and pin deployment workflow actions #267

Open

Description

@ffumero2003

Context

The tag-triggered Maven Central workflow needs explicit release checks and changelog-derived release notes. Workflow actions currently use mutable tags, and Javadoc publishing uses community actions.

Acceptance criteria

  • Pin every workflow action to an immutable commit and replace the Pages, status, and release community actions with official Pages actions, the GitHub status API, and gh release create.
  • Check release-tag/version/changelog agreement and membership in master before deployment.
  • Resolve the intended maintainers' registered public keys and run git verify-tag; warn by default and enforce only when ENFORCE_SIGNED_TAGS=true.
  • Hold deployment for open medium/high/critical findings, unreadable security data, or an incomplete/missing version milestone.
  • Preserve Maven Central, GPG artifact signing, Sonatype staging configuration, credentials, and the existing publication command.
  • Verify permitted and rejected paths locally, run Gradle build and the publication task graph with --dry-run, and document the required repository settings.

Scope

Workflow controls stacked on the release-documentation/Changie change. This work does not publish a release or change SDK behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions