ci: auto-build and release on new eclipse version#24
Open
F-Wer wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a scheduled GitHub Action that automatically checks for a new Eclipse JEE release and, when a new version is detected, builds the ADT bundle and publishes the ZIP as a GitHub Release asset.
What’s Included
New workflow: build-release-on-new-eclipse.yml
Trigger modes:
Manual trigger (workflow_dispatch)
Daily scheduled check (cron)
Workflow Behavior
Detects the latest Eclipse version from the Eclipse downloads page.
Checks if a release tag for that version already exists in this repo.
If no release exists:
Runs the Windows build (npm ci + npm start)
Publishes dist/eclipse-dist.zip via GitHub Release
If release exists, the build is skipped.
Why
This removes manual release checks and ensures new Eclipse versions are picked up and packaged automatically, reducing maintenance effort and release latency.
Notes
Release tag format used by the workflow: eclipse-YYYY-MM
Release asset uploaded: dist/eclipse-dist.zip