ci: publish a rolling dev prerelease from main - #89
Merged
Conversation
Adds dev-release.yml, which rebuilds the JAR on every non-documentation push to main and republishes it as the `dev` prerelease. This is what Dan's Plugin Manager's experimental release channel reads: /dpm get activitytracker --experimental fetches releases/tags/dev, so without a workflow like this there is nothing for it to download. This repository has no release.yml to mirror, so the build was run locally first to confirm that mvn clean package succeeds and leaves exactly one publishable JAR in target/. The JDK matches the one the existing CI workflow uses. The publish step deletes and recreates the release because editing a published release does not move its tag to the new commit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Part of the rollout behind Dan's Plugin Manager's experimental release channel. DPM can install main-branch builds with
/dpm get activitytracker --experimental, which readsreleases/tags/dev— this workflow publishes that release.Note on this repository specifically
Unlike the other plugins in this rollout, this repository has no
release.ymlwhose build steps could be mirrored. The build was therefore run locally first, andmvn clean packagewas confirmed to succeed and leave exactly one publishable JAR intarget/(the shade plugin'soriginal-*.jaris excluded, as it is elsewhere in the organisation). The JDK is set to 8 to match the existing CI workflow.What it does
On every push to
mainthat touches something other than documentation, the JAR is rebuilt and republished as a prerelease taggeddev. Because it is marked as a prerelease, GitHub's "latest release" is unaffected.target_commitish. Recreating with--target "$GITHUB_SHA"is what makesdev-<short sha>change between builds; without it every build would look identical and DPM would report "already up to date" forever..jarasset it finds and two JARs would make the installed build depend on asset order.Verification
The same workflow is already merged and confirmed working end to end on Medieval-Factions, AlternateAccountFinder, Currencies, FoodSpoilage, Herald and Dans-Essentials: each published release returns a 40-character commit sha in
target_commitish, DPM's parser turns it intodev-<short sha>, the JAR downloads anonymously over HTTP 200, andreleases/lateststill returns the real release.No CHANGELOG entry is included because this repository does not keep a
CHANGELOG.md.drafted by Claude on behalf of Daniel Stephenson