| Age | Commit message (Collapse) | Author |
|---|
|
Trying a build from another machine, typically the Windows Minecraft client,
meant starting ./x, then working out by hand which address the Colima port
forward is reachable on and whether the firewall lets it through. The skill
does that and reports LAN and Tailscale addresses, and warns that the
offline-mode server and RCON are open to anyone on that network.
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
The fix is a bug fix only, so it goes under a v1.4.1 heading. The tag scheme
notes now say "up to v1.4.0" instead of naming v1.5.0, because the next Paper
release is a patch and the boundary would otherwise point at a version that
may never ship.
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
correction-docs skills
release-lc replaces the release skill and carries a release through to a
published GitHub Release, a listed Modrinth version and live release notes,
since a pushed tag alone left drafts and broken links unnoticed. The other
skills cover the steps around it: writing the site release notes from
CHANGELOG.md, checking that the Paper and Velocity builds of the current tree
still handshake, and auditing the docs site against the source.
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
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>
|
|
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>
|
|
|
|
|
