Skip to content

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

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

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

Conversation

@GianTschingt

Copy link
Copy Markdown
Contributor

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

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-ehcache#7 (LDEV-6607).

What changes in .github/workflows/main.yml

  • The deploy job uploads the .lex files it built and published as the axis-release artifact.
  • A new job, github-release, runs after a successful deploy on a push or manual run (the deploy job itself still only runs on a push to the default branch). Pull request builds never create a release.
  • Skips -SNAPSHOT builds. They get no GitHub release.
  • Tag = exact published version (needs.setup.outputs.version, e.g. 1.5.0.9 or 1.5.0.9-RC). The release creates the tag on the built commit (--target $GITHUB_SHA); an existing tag with that name is reused.
  • Assets: axis-extension-<version>.lex (and .lite.lex if built).
  • Pre-releases 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 deploy still goes through.

actionlint reports no new findings 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 c35c80b into master Oct 22, 2026
13 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