All issues

Search results

Why are we getting double PRs from Scala Steward?

Status: Open.

#278 In scalacenter/sbt-version-policy;

· SethTisue opened on Jul 3, 2026

versionPolicyReportDependencyIssues requires versionPolicyIntention to be set

Status: Open.

#229 In scalacenter/sbt-version-policy;

· rtyley opened on Nov 22, 2024

False positive dependency error when upgrading to Scala 2.13.15 from 2.13.14

Status: Open.

#217 In scalacenter/sbt-version-policy;

· durban opened on Oct 5, 2024

Long loading time on multi-project

Status: Open.

#205 In scalacenter/sbt-version-policy;

· huajiang-tubi opened on Jun 7, 2024

TASTy-MiMa integration

Status: Open.

#204 In scalacenter/sbt-version-policy;

· grzegorz-bielski opened on May 8, 2024

Shouldn't releaseVersion always be ReleaseVersion.fromCompatibility(BinaryAndSourceCompatible) for sbt-release?

Status: Open.

#200 In scalacenter/sbt-version-policy;

· steinybot opened on Apr 9, 2024

Support declaring backwards compatibility with older versions outside of version scheme

Status: Open.

#198 In scalacenter/sbt-version-policy;

· lolgab opened on Mar 23, 2024

submodules released as über jars (eg from sbt-assembly) always have MissingClassProblems and None compatibility

Status: Open.

#190 In scalacenter/sbt-version-policy;

· rtyley opened on Dec 7, 2023

Only set mimaPreviousArtifacts when not set by other plugins

Status: Open.

#138 In scalacenter/sbt-version-policy;

· bjaglin opened on Sep 21, 2022

Avoid false positives versionCheck when versionScheme != early-semver

Status: Open.

#123 In scalacenter/sbt-version-policy;

· bjaglin opened on Mar 21, 2022

Idea: Factor out SBT-independent core module

Status: Open.

#120 In scalacenter/sbt-version-policy;

· nafg opened on Jan 6, 2022

Reporting mode (PoC available)

enhancementNew feature or requestNew feature or request

help wantedExtra attention is neededExtra attention is needed

Status: Open.

#119 In scalacenter/sbt-version-policy;

· nafg opened on Jan 3, 2022