.git-blame-ignore-revs

@@ -1,2 +1,5 @@
 # Scala Steward: Reformat with scalafmt 3.7.0
 c3efd683f835329e057719c1f2ededac55589933
+
+# Scala Steward: Reformat with scalafmt 3.7.15
+99aee8ec7e98cd260d674cca8f05505133e43d73

.github/release-drafter.yml

@@ -1,3 +1,39 @@
+name-template: 'v$RESOLVED_VERSION'
+tag-template: 'v$RESOLVED_VERSION'
+categories:
+  - title: '🔥 Breaking Changes'
+    labels:
+      - 'breaking'
+  - title: '🚀 Features'
+    labels:
+      - 'feature'
+      - 'enhancement'
+  - title: '🐛 Bug Fixes'
+    labels:
+      - 'bug'
+  - title: '👋 Deprecated'
+    labels:
+      - 'deprecation'
+  - title: '🔗 Dependency Updates'
+    labels:
+      - 'library-update'
+      - 'dependencies'
+  - title: '🛠  Internal Updates'
+    labels:
+      - 'internal'
+      - 'kaizen'
+      - 'test-library-update'
+      - 'sbt-plugin-update'
+  - title: '📚 Docs'
+    labels:
+      - 'doc'
+change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
+
+template: |
+  ## What's Changed
+  $CHANGES
+  **Full Changelog**: https://github.com/$OWNER/$REPOSITORY/compare/$PREVIOUS_TAG...v$RESOLVED_VERSION
+  
 autolabeler:
   - label: 'doc'
     files:

.github/workflows/test.yml

@@ -2,31 +2,23 @@ name: CI
 
 on:
   pull_request:
-    paths:
-      - '**.scala'
-      - '**.sbt'
-      - '.github/workflows/**.yml'
   push:
     branches:
       - master
-    paths:
-      - '**.scala'
-      - '**.sbt'
-      - '.github/workflows/**.yml'
 
 jobs:
   code_format:
     name: Code Format
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - name: scalafmt
         run: ./sbt scalafmtCheckAll
   test_jdk11:
     name: Test JDK11
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - uses: actions/setup-java@v3
         with:
           distribution: 'temurin'
@@ -37,7 +29,7 @@ jobs:
     name: Test JDK17
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - uses: actions/setup-java@v3
         with:
           distribution:	'temurin'

.mergify.yml

@@ -0,0 +1,18 @@
+pull_request_rules:
+  - name: Automatic merge Scala Steward PRs
+    conditions:
+      - author=xerial-bot
+      - check-success=Code Format
+      - check-success=Test JDK11
+      - check-success=Test JDK17
+      - or:
+        - title~=^Update airframe-
+        - title~=^Update sbt-airframe
+        - title~=^Update airspec
+        - title~=^Update scalafmt-core
+        - label=sbt-plugin-update
+        - label=test-library-update
+        - label=library-update  
+    actions:
+      merge:
+        method: squash

.scala-steward.conf

@@ -1 +1,2 @@
-updates.ignore = [ { groupId = "org.scala-sbt" } ]
+# sbt plugins must use Scala 2.12.x
+updates.pin  = [ { groupId = "org.scala-lang", artifactId="scala-library", version = "2.12." } ]

.scalafmt.conf

@@ -1,4 +1,4 @@
-version = 3.7.3
+version = 3.7.15
 project.layout = StandardConvention
 runner.dialect = scala212
 maxColumn = 120

README.md

@@ -7,12 +7,12 @@ A sbt plugin for publishing your project to the Maven central repository through
     * Create GPG signed artifacts to a local staging repository.
     * Make sure adding `publishTo := sonatypePublishToBundle.value` to your build.sbt
  * `sonatypeBundleRelease` (New in sbt-sonatype 3.4)
-    * This command will prepare a new remote staging repository at Sonatype. If there are exisiting staging repositories that have the same description with `sonatypeSessionName` key, sbt-sonatype will discard them properly.
+    * This command will prepare a new remote staging repository at Sonatype. If there are  existing staging repositories that have the same description with `sonatypeSessionName` key, sbt-sonatype will discard them properly.
     * Then, it will upload the artifacts in the local staging folder to the remote staging repository. Uploading artifacts as a bundle is much faster than uploading each artifact to Sonatype. For example, thousands of files can be uploaded in several minutes with bundle upload.
-    * Finally, this command will perform the close and release steps at the Sonatype Nexus repository to verify the Maven central requirements.
+    * Finally, this command will perform the close and release steps at the Sonatype Nexus repository to meet the Maven central requirements.
 
  After these steps, your project will be synchronized to the Maven central within ten minutes. No longer need to enter the web interface of
- [Sonatype Nexus repository](http://oss.sonatype.org/) to performe these release steps.
+ [Sonatype Nexus repository](http://oss.sonatype.org/) to perform these release steps.
 
 
 - [Release notes](ReleaseNotes.md)
@@ -109,7 +109,7 @@ credentials += Credentials("Sonatype Nexus Repository Manager",
 sbt-sonatype is an auto-plugin, which will automatically configure your build. There are a few settings though that you need to define by yourself:
 
   * `sonatypeProfileName`
-     * This is your Sonatype acount profile name, e.g. `org.xerial`. If you do not set this value, it will be the same with the `organization` value.
+     * This is your Sonatype account profile name, e.g. `org.xerial`. If you do not set this value, it will be the same with the `organization` value.
   * `pomExtra`
      * A fragment of Maven's pom.xml. You must define url, licenses, scm and developers tags in this XML to satisfy [Central Repository sync requirements](http://central.sonatype.org/pages/requirements.html).
 
@@ -166,7 +166,7 @@ Usually, we only need to run `sonatypeBundleRelease` command in sbt-sonatype:
 
 ### Individual Step Commands
 * __sonatypePrepare__
-  * Drop the exising staging repositories (if exist) and create a new staging repository using `sonatypeSessionName` as a unique key.
+  * Drop the existing staging repositories (if exist) and create a new staging repository using `sonatypeSessionName` as a unique key.
   * This will update `sonatypePublishTo` setting.
   * For cross-build projects, make sure running this command only once at the beginning of the release process.
     * Usually using sonatypeBundleUpload should be sufficient, but if you need to parallelize artifact uploads, run `sonatypeOpen` before each upload to reuse the already created stging repository.
@@ -184,7 +184,7 @@ Usually, we only need to run `sonatypeBundleRelease` command in sbt-sonatype:
 * __sonatypeReleaseAll__ (sonatypeProfileName)?
   * Close and promote all staging repositories (Useful for cross-building projects)
 
-## Other Commmands
+## Other Commands
 * __sonatypeBundleClean__
   * Clean a local bundle folder
 * __sonatypeClean__

build.sbt

@@ -16,8 +16,14 @@
 
 Global / onChangedBuildSource := ReloadOnSourceChanges
 
+// Must use Scala 2.12.x for sbt plugins
+val SCALA_VERSION = "2.12.18"
+
 ThisBuild / dynverSeparator := "-"
 
+// Set scala version for passing scala-steward run on JDK20
+ThisBuild / scalaVersion := SCALA_VERSION
+
 lazy val buildSettings: Seq[Setting[_]] = Seq(
   organization         := "org.xerial.sbt",
   organizationName     := "Xerial project",
@@ -35,7 +41,7 @@ lazy val buildSettings: Seq[Setting[_]] = Seq(
   }
 )
 
-val AIRFRAME_VERSION = "23.5.3"
+val AIRFRAME_VERSION = "23.11.3"
 
 // Project modules
 lazy val sbtSonatype =

project/build.properties

@@ -1 +1 @@
-sbt.version=1.8.2
+sbt.version=1.9.7

project/plugins.sbt

@@ -1,8 +1,8 @@
-val SONATYPE_VERSION = sys.env.getOrElse("SONATYPE_VERSION", "3.9.20")
+val SONATYPE_VERSION = sys.env.getOrElse("SONATYPE_VERSION", "3.9.21")
 addSbtPlugin("org.xerial.sbt" % "sbt-sonatype"  % SONATYPE_VERSION)
 addSbtPlugin("com.github.sbt" % "sbt-pgp"       % "2.2.1")
-addSbtPlugin("org.scalameta"  % "sbt-scalafmt"  % "2.5.0")
-addSbtPlugin("com.dwijnand"   % "sbt-dynver"    % "4.1.1")
+addSbtPlugin("org.scalameta"  % "sbt-scalafmt"  % "2.5.2")
+addSbtPlugin("com.github.sbt" % "sbt-dynver"    % "5.0.1")
 addSbtPlugin("com.eed3si9n"   % "sbt-buildinfo" % "0.11.0")
 
 libraryDependencies += "org.scala-sbt" %% "scripted-plugin" % sbtVersion.value

sbt

@@ -34,11 +34,11 @@
 
 set -o pipefail
 
-declare -r sbt_release_version="1.6.2"
-declare -r sbt_unreleased_version="1.6.2"
+declare -r sbt_release_version="1.9.7"
+declare -r sbt_unreleased_version="1.9.7"
 
-declare -r latest_213="2.13.8"
-declare -r latest_212="2.12.15"
+declare -r latest_213="2.13.12"
+declare -r latest_212="2.12.18"
 declare -r latest_211="2.11.12"
 declare -r latest_210="2.10.7"
 declare -r latest_29="2.9.3"