Skip to content

docs(tlibs): fold the TLibs release notes into the project index #95

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ryanbarlow97 merged 1 commit into from
Oct 3, 2026
Merged

docs(tlibs): fold the TLibs release notes into the project index #95

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions projects/TLibs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,13 @@ with the matching consumers before deployment.

See the [shared pipeline guide](../../PIPELINES.md) for development artifacts, release tags, dependency selection and rollback.

TLibs releases follow that process: a `v*` tag supplies the version, and the
release workflow verifies the build and uploads the runtime JAR, `SHA256SUMS` and
`build.json` to a draft release for review. TLibs' own workflows run the
`setup-plugins` action from the checkout being built, whereas consumers pin it to
a reviewed TLibs commit SHA. Build and release runs also upload the JaCoCo
coverage report.

Consumers use `me.plugins:tlibs` with Maven `provided` scope. The
[shared installer](https://github.com/TF-Minecraft/TLibs/blob/main/DEPENDENCIES.md)
verifies plugin release hashes and installs exact coordinates without recursively
Expand Down