[Tooling]: Pin the Java toolchain and add contribution docs - #122
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[Tooling]: Pin Java toolchainAdds
mise.tomlpinningjava = "temurin-21.0.12+101.0.LTS".The repository has had no toolchain pin, so every contributor's JDK came from whatever their global config or
PATHhappened to provide. CI already standardises on Temurin 21 (actions/setup-java@v4inandroid.yml,desktop.ymlandrelease.yml); this makes a local checkout match without relying on a developer's global mise config.Verified locally — with the file in place,
mise config lsreports the repository config alongside the global one andmise exec -- java -versionresolves to Temurin 21.0.12.[Docs]: Add community contribution guidanceAdds
CONTRIBUTING.md(module boundaries, development setup, JVM-target and credential-hygiene rules, PR expectations) andCODE_OF_CONDUCT.md(Contributor Covenant 3.0, with private reporting through VinnovateIT maintainer channels).SECURITY.mdandREADME.mdare already onmain; these are the two remaining standard community health files GitHub looks for.Notes
No build files are touched — Gradle does not read
mise.toml, so this cannot affect CI behaviour or the resolved dependency graph.