Skip to content

ci: publish to the Set Homes listing as SetHomes.V<x>.jar - #64

Merged
milanmalhotra merged 1 commit into
devfrom
issue-55-publish-to-set-homes-listing
Aug 18, 2026
Merged

ci: publish to the Set Homes listing as SetHomes.V<x>.jar#64
milanmalhotra merged 1 commit into
devfrom
issue-55-publish-to-set-homes-listing

Conversation

@milanmalhotra

Copy link
Copy Markdown
Collaborator

Closes #55.

Points the release pipeline at BukkitDev project 312833, the existing Set Homes listing, so every v1 server is offered v2 as an update on the page it already watches. The published jar and the GitHub Release become SetHomes.V<x>.jar and Set Homes V<x>. scripts/publish-bukkitdev.sh had a comment naming the two project ids the wrong way round, which is corrected.

The extra bit: a version floor

Not in the issue's change table, added after reading the release path.

v1 last shipped 1.3.1 and pom.xml is at 1.2.2. release.yml publishes on any push to master, and the 2.0.0 bump is a by-hand item still open on #41 because changesets in this repo are always patch. So repointing the listing on its own makes it possible to publish "Set Homes V1.2.3" onto the v1 listing, offered as an update to servers running 1.3.1.

publish-bukkitdev.sh now refuses anything below 2.0.0, in the same style as the game-version count check right above it. Promoting dev before the manual major bump becomes a failed release step instead of a public downgrade.

That failure mode is not hypothetical. Running the test harness before this change, the VERSION=1.2.3 case ran to completion and printed BukkitDev upload succeeded (HTTP 200).

Verification

  • scripts/test-publish-bukkitdev.sh: 6 passed / 4 failed before, 10 passed / 0 failed after. Two new cases cover the guard: a sub-2.0.0 run exits non-zero, and records no curl call at all.
  • Boundaries: 0.x and 1.x refuse; 2.0.0 and 10.0.0 pass (1.* needs a literal dot, so 10.0.0 is not caught).
  • mvn test: 387 tests, 0 failures, 0 errors, 0 skipped, unchanged before and after.
  • grep -rn "913275\|SetHomesTwo\.V\|SetHomesTwo V" .github/ scripts/ returns nothing.

Still owed, since it needs Actions: a Release workflow dry_run dispatch confirming project 312833, jar SetHomes.V<x>.jar, title Set Homes V<x>.

Out of scope

plugin.yml's name:, the plugins/SetHomesTwo/ data folder and the Maven artifact name are all unchanged, per the issue. The README rename, the 2.0.0 bump, retitling 312833 and retiring 913275 stay on #41.

Point the release at BukkitDev project 312833, the listing v1 servers
already watch, so v2 arrives as the update on the page they know rather
than a download they have to go and find. The published artifact and the
GitHub Release become SetHomes.V<x>.jar and "Set Homes V<x>". The script
comment named the two project ids the wrong way round; that is corrected.

Also refuse to publish anything below 2.0.0. v1 last shipped 1.3.1 and
the pom is at 1.2.2, so until the major bump is made by hand at promotion
a push to master would offer those servers a lower version than they are
running. The guard turns that into a failed release step instead of a
public downgrade, and sits beside the existing game-version sanity check.

plugin.yml's name, the data folder and the Maven artifact are unchanged.
@milanmalhotra
milanmalhotra merged commit e5b1f64 into dev Aug 18, 2026
7 checks passed
@milanmalhotra
milanmalhotra deleted the issue-55-publish-to-set-homes-listing branch August 18, 2026 14:41
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.

1 participant