LunaticChat.git/website/src/ja/changelog, branch main A next-generation chat plugin for Paper, Folia and Velocity. ci: link release notes to the English changelog pages 2026-08-04T19:54:20+00:00 Sho Sakuma me@m1sk9.dev 2026-08-04T19:54:20+00:00 004cf9308b5d98737125509adee08b9018cce964 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> 
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>
docs: add changelog pages to the documentation site 2026-08-04T19:37:05+00:00 Sho Sakuma me@m1sk9.dev 2026-08-04T19:37:05+00:00 8bff9150039b4d94830e43d0688bc03c6a082e64 Release notes were written into the GitHub release body, which means they exist once, in English only, and are awkward to revise after publishing. Putting them on the site gives each release a Japanese and an English page that can be corrected later and linked from anywhere. The overview page states the versioning rules the version numbers alone do not convey: that dropping a supported platform is a MINOR bump, that the Paper and Velocity builds advance separately, and that the plugin version says nothing about compatibility. Co-Authored-By: Claude <noreply@anthropic.com> 
Release notes were written into the GitHub release body, which means they exist
once, in English only, and are awkward to revise after publishing. Putting them
on the site gives each release a Japanese and an English page that can be
corrected later and linked from anywhere.

The overview page states the versioning rules the version numbers alone do not
convey: that dropping a supported platform is a MINOR bump, that the Paper and
Velocity builds advance separately, and that the plugin version says nothing
about compatibility.

Co-Authored-By: Claude <noreply@anthropic.com>