Scala Version Pinned
scala.scala-version-pinned
Ensures the Scala compiler version is declared (scalaVersion := "..."
in build.sbt, the equivalent in build.sc, or <scala.version> /
<scala.binary.version> in pom.xml). Pinning the compiler version
prevents drift between developers and CI.
Compatible Integrations
This guardrail works with the following integrations. Click to see how to use Scala Version Pinned with each collector.
Enable This Guardrail
Add the parent policy to your lunar-config.yml to enable this guardrail.
policies:
- uses: github://earthly/lunar-lib/policies/scala@v1.0.5
include: [scala-version-pinned]
# with: ...How This Guardrail Works
This guardrail is part of the Scala Project Guardrails policy. It evaluates data collected by integrations and produces a pass/fail check with actionable feedback.
When enabled, this check runs automatically on every PR and in AI coding workflows, providing real-time enforcement of your engineering standards.
Learn How Lunar Works →Configuration Options
These inputs can be configured in your lunar-config.yml to customize
how the parent policy (and this guardrail) behaves.
| Input | Required | Default | Description |
|---|---|---|---|
min_scala_version
|
Optional |
2.12
|
Minimum required Scala compiler version (e.g., "2.12", "2.13", "3.3.1"). Compared with semantic-version semantics — "2.13" matches 2.13.x and 3.x, but rejects 2.11.x. |
min_sbt_version
|
Optional |
1.9
|
Minimum required sbt version (e.g., "1.9", "1.10.0"). Compared with semantic-version semantics. Skipped when the project does not use sbt. |
Scala Project Guardrails
This guardrail is part of the Scala Project Guardrails policy, which includes 8 guardrails for devex build and ci.
Ready to Automate Your Standards?
See how Lunar can turn your AGENTS.md, engineering wiki, compliance docs, or postmortem action items into automated guardrails with our 200+ built-in guardrails.
AI agent rules & prompt files
Post-mortem action items
Security & compliance policies
Testing & quality requirements