Skip to content

chore: stop tracking .java-version - #45

Merged
gvonnessi merged 1 commit into
mainfrom
chore/untrack-java-version
Jul 9, 2026
Merged

gvonnessi merged 1 commit into
mainfrom
chore/untrack-java-version

Conversation

@gvonnessi

Copy link
Copy Markdown
Collaborator

Summary

  • Remove .java-version from version control. It pins an exact JDK patch release (21.0.6), which goes stale on every brew upgrade and differs between machines — developer-local state, not a project contract.
  • Add /.java-version to .gitignore, anchored to the repo root to match the existing rule style (/.claude, /.bsp).
  • Terminate .gitignore with a newline. Cosmetic; git parses an unterminated final line correctly either way.

The file stays on disk for local jenv use — this only stops git tracking it.

Test plan

  • CI green on both required checks: Scala 2.13 and 3, temurin@21
  • sbt githubWorkflowCheck passes locally — ci.yml still matches build.sbt
  • CI does not read the file: ci.yml pins java-version: 21 directly via actions/setup-java, not java-version-file:
  • git check-ignore confirms both /.java-version and /.claude resolve
  • jenv version in the repo still reports 21 from the on-disk file

The jenv pin names an exact JDK patch release, so it goes stale on every
brew upgrade and differs between machines. It is developer-local state,
not a project contract.

CI is unaffected: ci.yml pins temurin@21 directly via actions/setup-java
rather than reading java-version-file.
@gvonnessi
gvonnessi merged commit ec2c52a into main Jul 9, 2026
9 checks passed
@gvonnessi
gvonnessi deleted the chore/untrack-java-version branch July 9, 2026 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant