Update dependency com.github.sbt:sbt-ci-release to v1.9.2 #760
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.
Release Notes
sbt/sbt-ci-release (com.github.sbt:sbt-ci-release)
v1.9.2
Compare Source
v1.9.1
: 1.9.1Compare Source
sbt-ci-release 1.9.1 is cross published to:
bug fix
version
to project by @eed3si9n in https://github.com/sbt/sbt-ci-release/pull/338behind the scene
new contributors
Full Changelog: sbt/sbt-ci-release@v1.9.0...v1.9.1
v1.9.0
: 1.9.0Compare Source
sbt-ci-release 1.9.0 is cross published to:
tag-based back publishing
See https://eed3si9n.com/tag-based-back-publishing-with-sbt/ for details.
behind the scene
new contributors
Full Changelog: sbt/sbt-ci-release@v1.8.0...v1.9.0
v1.8.0
: 1.8.0Compare Source
sbt-ci-release 1.8.0 is cross published to:
about sbt-ci-release
sbt-ci-release is an sbt plugin, originally created by @olafurpg in 2018, to automate releases to Sonatype and Maven Central from GitHub Actions by composing four existing sbt plugins sbt-dynver, sbt-git, sbt-pgp, and sbt-sonatype, which in turn were created by dwijnand, jsuereth, and xerial respectively.
sbt 2.x migration
Cross building of sbt-ci-release to sbt 2.x was implemented by @eed3si9n in https://github.com/sbt/sbt-ci-release/pull/321. This combines the ongoing effort of the upstream plugin migrations:
behind the scene
sbt/setup-sbt@v1
by @SethTisue in https://github.com/sbt/sbt-ci-release/pull/318Full Changelog: sbt/sbt-ci-release@v1.7.0...v1.8.0
v1.7.0
: 1.7.0Compare Source
updates
behind the scece
new contributors
Full Changelog: sbt/sbt-ci-release@v1.6.1...v1.7.0
v1.6.1
: 1.6.1Compare Source
bug fix
Full Changelog: sbt/sbt-ci-release@v1.6.0...v1.6.1
v1.6.0
: 1.6.0Compare Source
Sonatype Central Portal support
In 2024, Sonatype, the company that runs Maven Central, started rolling out a new backend called Central Portal, which has its own publishing API called Publisher Portal API. To support this new endpoint for Scala, @Andrapyre created lumidion/sonatype-central-client.
sbt-ci-release 1.6.0 updates sbt-sonatype to 3.11.2, which in turn depends on sonatype-central-client (upickle version). The update was contributed by @KacperFKorban in https://github.com/sbt/sbt-ci-release/pull/303
behind the scene
ubuntu-latest
instead ofubuntu-20.04
by @xuwei-k in https://github.com/sbt/sbt-ci-release/pull/290New Contributors
Full Changelog: sbt/sbt-ci-release@v1.5.12...v1.6.0
v1.5.12
: sbt-ci-release v1.5.12Compare Source
What's Changed
New Contributors
Full Changelog: sbt/sbt-ci-release@v1.5.11...v1.5.12
v1.5.11
: sbt-ci-release v1.5.11Compare Source
What's Changed
New Contributors
Full Changelog: sbt/sbt-ci-release@v1.5.10...v1.5.11
Configuration
📅 Schedule: Branch creation - "on the 1st through 7th day of the month" in timezone America/Los_Angeles, 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.
This PR was generated by Mend Renovate. View the repository job log.