Skip to content

chore(deps): update dependency com.github.sbt:sbt-ci-release to v1.11.2#132

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/com.github.sbt-sbt-ci-release-1.x
Open

chore(deps): update dependency com.github.sbt:sbt-ci-release to v1.11.2#132
renovate[bot] wants to merge 1 commit intomainfrom
renovate/com.github.sbt-sbt-ci-release-1.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 12, 2025

This PR contains the following updates:

Package Type Update Change
com.github.sbt:sbt-ci-release (source) plugin minor 1.9.21.11.2

Release Notes

sbt/sbt-ci-release (com.github.sbt:sbt-ci-release)

v1.11.2: 1.11.2

Compare Source

sbt-ci-release 1.11.2 is cross published to:

sbt Version Published
1.x
2.x

about sbt-ci-release

sbt-ci-release is an sbt plugin, originally created by @​olafurpg in 2018, to automate releases to the Central Repo from GitHub Actions by composing three existing sbt plugins sbt-dynver, sbt-git, and sbt-pgp, which in turn were created by dwijnand and jsuereth.

update

behind the scene

Full Changelog: sbt/sbt-ci-release@v1.11.1...v1.11.2

v1.11.1: 1.11.1

Compare Source

updates

  • fix: Fixes SNAPSHOT publishing to run +publish, as opposed to publish by @​eed3si9n in #​381

behind the scene

new contributors

Full Changelog: sbt/sbt-ci-release@v1.11.0...v1.11.1

v1.11.0: 1.11.0

Compare Source

breaking change: Central Portal support

sbt-ci-release 1.11.0 defaults to publishing to the Central Portal using sbt 1.11.0 since the Legacy OSSRH endpoint is planned to be sunset on June 30th 2025. Additionally, ThisBuild / sbtPluginPublishLegacyMavenStyle := false is included since the Central Portal no longer supports POM inconsistent layout.

This was implemented by @​eed3si9n in #​365 / #​368 / #​370

How to publish to Legacy OSSRH

Until June 2025, either use sbt-ci-release 1.9.3, or the following configuration to publish to the Legacy OSSRH endpoint.

  1. Add sbt-sonatype 3.12.2 to project/plugins.sbt
  2. Add publishTo := sonatypePublishToBundle.value to build.sbt
  3. Change CI_SONATYPE_RELEASE environment variable to sonatypeBundleRelease in the GitHub Actions

behind the scene

Full Changelog: sbt/sbt-ci-release@v1.9.3...v1.11.0

v1.9.3: 1.9.3

Compare Source

updates and fixes

  • fix: Fix tag-based publishing accidentally dropping sbt-dynver suffix @​eed3si9n in #​358

behind the scene

Full Changelog: sbt/sbt-ci-release@v1.9.2...v1.9.3


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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 force-pushed the renovate/com.github.sbt-sbt-ci-release-1.x branch from 9a0645e to a5d7a93 Compare May 24, 2025 09:42
@renovate renovate bot changed the title chore(deps): update dependency com.github.sbt:sbt-ci-release to v1.9.3 chore(deps): update dependency com.github.sbt:sbt-ci-release to v1.11.0 May 24, 2025
@renovate renovate bot force-pushed the renovate/com.github.sbt-sbt-ci-release-1.x branch from a5d7a93 to 80f7f54 Compare June 2, 2025 01:31
@renovate renovate bot changed the title chore(deps): update dependency com.github.sbt:sbt-ci-release to v1.11.0 chore(deps): update dependency com.github.sbt:sbt-ci-release to v1.11.1 Jun 2, 2025
@renovate renovate bot force-pushed the renovate/com.github.sbt-sbt-ci-release-1.x branch from 80f7f54 to 52965af Compare August 17, 2025 10:23
@renovate renovate bot changed the title chore(deps): update dependency com.github.sbt:sbt-ci-release to v1.11.1 chore(deps): update dependency com.github.sbt:sbt-ci-release to v1.11.2 Aug 17, 2025
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.

0 participants