Skip to content

chore(deps): update dependency sbt/sbt to v1.11.0 #4897

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 26, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 26, 2025

This PR contains the following updates:

Package Update Change
sbt/sbt minor 1.10.11 -> 1.11.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

sbt/sbt (sbt/sbt)

v1.11.0: 1.11.0

Compare Source

Central Repository publishing

The Central Repository (aka Maven Central) has long been the pillar of the JVM ecosystem including Scala. The mechanism to publish libraries to the Central has been hosted by Sonatype as OSS Repository Hosting (OSSRH) via HTTP PUT, but in March it was announced that the endpoint will be sunset in June 2025 in favor of the Central Portal at https://central.sonatype.com/.

sbt 1.11.0 implements a built-in support to publish to Central Repository via the Central Portal. To publish to the Central Portal, first set ThisBuild / publishTo setting to the localStaging repository:

ThisBuild / publishTo := {
  val centralSnapshots = "https://central.sonatype.com/repository/maven-snapshots/"
  if (isSnapshot.value) Some("central-snapshots" at centralSnapshots)
  else localStaging.value
}

Add credentials to the host central.sonatype.com using the generated user token user name and password. When you're ready to publish, call publishSigned task (available via sbt-pgp). At this point, the JARs and POM files will be staged to your local target/sona-staging directory.

Next, call sonaUpload to upload to the Central Portal and manually release the bundle, or call sonaRelease to upload and automatically release to the Central Repository.

This was contributed by @​eed3si9n in #​8126. The feature was inspired by sbt-sonatype workflow pioneered by Taro Saito, and sonatype-central-client spearheaded by David Doyle at Lumidion.

Other updates

Full Changelog: sbt/sbt@v1.10.11...v1.11.0


Configuration

📅 Schedule: Branch creation - "after 4pm on friday,before 9am on monday,every weekend" in timezone Europe/Paris, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner May 26, 2025 00:45
@renovate renovate bot requested review from morganleroi and Fluf22 and removed request for a team May 26, 2025 00:45
@algolia-bot
Copy link
Collaborator

algolia-bot commented May 26, 2025

🪓 The generated code will be pushed at the end of the CI.

Action triggered by commit 0d42ac8a9253bc9561ffdd262f953efaecde0416.

Please do not push any generated code to this pull request.

@renovate renovate bot force-pushed the renovate/sbt-sbt-1.x branch 2 times, most recently from 2de1411 to ca3de6f Compare May 26, 2025 01:10
@renovate renovate bot force-pushed the renovate/sbt-sbt-1.x branch from ca3de6f to 7c817e7 Compare May 26, 2025 01:18
@renovate renovate bot merged commit 51c6e90 into chore/renovateBaseBranch May 26, 2025
1 check passed
@renovate renovate bot deleted the renovate/sbt-sbt-1.x branch May 26, 2025 01:21
algolia-bot added a commit that referenced this pull request May 26, 2025
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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