Skip to content

LDEV-6681 GitHub release with .lex for every final, ALPHA, BETA and RC build - #18

Merged
michaeloffner merged 1 commit into
masterfrom
LDEV-6681-github-release
Oct 22, 2026
Merged

michaeloffner merged 1 commit into
masterfrom
LDEV-6681-github-release

Conversation

@GianTschingt

Copy link
Copy Markdown
Contributor

https://luceeserver.atlassian.net/browse/LDEV-6681

Every final, ALPHA, BETA and RC build that gets published now also becomes a GitHub release with its .lex files attached, so ext.lucee.org can redirect extension downloads to GitHub releases (LDEV-6511). Same approach as lucee/extension-s3#27 (LDEV-6604).

What changes: a new job, github-release, in .github/workflows/main.yml

  • Runs after a successful deploy under the same condition as the Maven Central / S3 upload (needs.setup.outputs.publish == 'true': push or manual run on master/main, a version branch or release/*).
  • Skips -SNAPSHOT builds. They get no GitHub release.
  • Tag = exact published version (needs.setup.outputs.version, e.g. 3.1.0.2 or 3.1.0.2-RC). The release creates the tag on the built commit (--target $GITHUB_SHA); an existing tag with that name is reused.
  • Assets: esapi-extension-<version>.lex and .lite.lex (if built), taken from the esapi-s3 artifact, so they are the same files the S3 job uploads.
  • ALPHA/BETA/RC are marked --prerelease --latest=false. Finals built from the default branch are marked --latest; finals from any other branch are --latest=false.
  • Idempotent: if the release already exists (for example on a re-run), the assets are re-uploaded with --clobber.
  • GITHUB_TOKEN with contents: write on this job only. No new secrets, no hardcoded URLs or versions.
  • It's a separate job, so if it fails, the Maven Central and S3 uploads still go through.

actionlint passes on the changed workflow.

The historical non-SNAPSHOT versions from ext.lucee.org and Maven Central have been added as GitHub releases separately.

@michaeloffner
michaeloffner merged commit 726a140 into master Oct 22, 2026
17 checks passed
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.

2 participants