Skip to content

ci: replace unverified third-party GitHub Actions with first-party steps - #271

Draft
ffumero2003 wants to merge 1 commit into
masterfrom
ci-vendor-third-party-actions
Draft

ffumero2003 wants to merge 1 commit into
masterfrom
ci-vendor-third-party-actions

Conversation

@ffumero2003

Copy link
Copy Markdown
Contributor

Context

Part of the organization-wide GitHub Actions governance effort: actions owned by individual developers should not run in our CI/CD. This replaces each such action with a first-party step we control. GitHub-official and verified-vendor actions, and the package publish steps, are unchanged.

Changes

  • softprops/action-gh-release (deploy.yml) → gh release create (reruns via gh release edit + gh release upload --clobber), preserving tag, title, notes, and flags.
  • crazy-max/ghaction-github-pages (ci_cd.yml) → an inline git push of the built Javadoc to the gh-pages branch. The build job gains permissions: contents: write, required for that push.
  • crazy-max/ghaction-github-status (ci_cd.yml) → a read-only query of the githubstatus.com API for the Pages component, preserving the major_outage threshold. (The original action set no commit status, so none is created.)
  • Each original action block is retained commented-out as an instant fallback, pending a verified real run.

Verification

  • Changelog/command checks: the Pages-status and Javadoc smoke checks pass locally; gh release command routing verified.
  • Fork dry-run on a real runner: the Pages health gate reported operational; the Javadoc deploy published 352 files to the fork's gh-pages; gh release create and its --clobber rerun succeeded (same release id, assets replaced); and the Maven/GH-Packages publish steps correctly skipped (guarded to the private repository). Cleanup completed; the canonical repository was untouched.
  • Scope: the build command and both Maven publish steps are byte-identical to master; actionlint introduces no new diagnostics versus master (the remaining SC2035/SC2086 notes pre-exist on master).
  • Not verified until a real run: the Javadoc deploy and status gate run on push to master, so they first execute on merge; gh release create runs only at a tagged release. The commented-out originals remain as a fallback until those first runs are green.

Closes #270

Use GitHub CLI and inline run steps for releases, Pages health checks, and gh-pages publishing. Retain the original action blocks as commented fallbacks and keep build and Maven publish commands unchanged.
@ffumero2003 ffumero2003 self-assigned this Nov 18, 2026
@ffumero2003
ffumero2003 marked this pull request as draft November 19, 2026 16:48
@ffumero2003

Copy link
Copy Markdown
Contributor Author

Converting to draft and parking this. On hold pending internal coordination on this repo's ownership; the branch and work are preserved to revisit later. Not for merge in the meantime.

This branch has not been deployed

No deployments
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.

ci: replace unverified third-party GitHub Actions with first-party steps

1 participant