summaryrefslogtreecommitdiff
path: root/.github/workflows/release-paper.yaml
AgeCommit message (Collapse)Author
2026-08-05ci: link release notes to the English changelog pagesSho Sakuma
The links were written before the English pages existed, so GitHub and Modrinth sent an international audience to Japanese notes. Both now point at the English pages; the Japanese ones remain reachable from the site's own locale switch. Also stops the changelog template from being served. It lives under `src/`, so VitePress published it as a page of empty headings at /assets/changelog-default, where it was reachable and indexable. `srcExclude` keeps it a template. The tag table on the changelog overview claimed `vX.Y.Z` was last used for v1.0.0 and retired, which contradicts release.yaml and the release skill still supporting it; it now says what the tag is for. Co-Authored-By: Claude <noreply@anthropic.com>
2026-08-05ci: point release notes at the documentation siteSho Sakuma
Every release emitted a skeleton of six empty headings that had to be filled in by hand on the draft, and Modrinth linked to the GitHub release, so a reader needed two hops to reach notes that might never have been written. Both now link straight to the changelog page for the released version, built from the tag, so the notes live in exactly one place. This makes the release depend on that page being deployed, which the release skill now checks for. Co-Authored-By: Claude <noreply@anthropic.com>
2026-08-02feat: support Paper 26.2 (Minecraft 26.2)Sho Sakuma
Paper 26.2 bundles Adventure 5.2.0, a major bump from the 4.26.1 shipped by 26.1. Adventure 5 makes ClickEvent generic, so the raw type in CommandContext.replyWithEvent no longer compiled. Auditing the rest of the Adventure 5 removals found no other affected usage. api-version is raised to 26.2, dropping 26.1 support: the two Adventure majors are not binary compatible, so claiming 26.1 compatibility would be a lie. Also fixes two problems found while verifying on a real server: the Velocity healthcheck invoked mc-health, which does not exist in the mc-proxy image, so the container had never once passed its check; and the debug environments pinned no build at all, which meant the proxy came up as 4.1.0-SNAPSHOT while the plugin is compiled against velocity-api 3.5.1. Server versions are now derived by x from the Gradle coordinates so they cannot drift from what the plugin targets.
2026-05-28chore(deps): update cloudnode-pro/modrinth-publish digest to 8dc596brenovate[bot]
2026-05-06chore(release): prepare paper v1.2.0 for paper 26.1.2 supportSho Sakuma
- Bump paperVersion to 1.2.0 - Update docker compose files to Paper/Folia 26.1.2 - Add v1.2.0 entry to CHANGELOG - Drop "LunaticChat" prefix from release titles Co-Authored-By: Claude <noreply@anthropic.com>
2026-05-06docs: clarify paper/velocity compatibilitySho Sakuma
Add a dynamic compatibility matrix (GitHub Releases + ProtocolVersion.kt at each tag) shown on the home page, download page, and a new reference doc. Split protocol theory and rolling-update rules out of the Velocity feature guide into the new compatibility reference, and simplify the download notice. Also set explicit GitHub release titles in the Paper / Velocity workflows so the awkward paper/v* tag prefix is not the user-facing label. Co-Authored-By: Claude <noreply@anthropic.com>
2026-04-29chore(deps): update cloudnode-pro/modrinth-publish digest to a913fbdrenovate[bot]
2026-04-07fix(ci): add download path for release artifactSho Sakuma
download-artifact without path extracts the JAR to the repo root, but gh release create expects it under platform-*/build/libs/. Co-Authored-By: Claude <noreply@anthropic.com>
2026-04-04feat: Improving Velocity's Cycling CompatibilitySho Sakuma