Skip to content

Update sbt-ci-release to 1.11.0 #959

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

Conversation

scala-steward
Copy link
Contributor

About this PR

πŸ“¦ Updates com.github.sbt:sbt-ci-release from 1.9.3 to 1.11.0

πŸ“œ GitHub Release Notes - Version Diff

Usage

βœ… Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

βš™ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "com.github.sbt", artifactId = "sbt-ci-release" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.sbt", artifactId = "sbt-ci-release" }
}]
labels: sbt-plugin-update, early-semver-minor, semver-spec-minor, commit-count:1

@saeltz
Copy link
Collaborator

saeltz commented May 25, 2025

@mccartney, do you have sufficient permissions to do the change for publishing to Sonatype Central? The existing method won't work anymore after June 30th.

@mccartney
Copy link
Collaborator

I likely do not. I haven't migrated any other project yet. But for Scapegoat I don't have the credentials to Sonatype.
I am not sure what exactly is needed to set up the new way. I.e. if we need to ask @sksamuel or are we good on our own.

@saeltz
Copy link
Collaborator

saeltz commented May 25, 2025

We at least need to change environment variables of GitHub Actions to update this plugin. Do you have access to that?

@mccartney
Copy link
Collaborator

I don't have it either.

@Johnnei
Copy link
Contributor

Johnnei commented May 25, 2025

I think the credentials that were set in #851 should already work for the new central portal.
So we might be able to fix it by reassigning env vars during the script, but haven't tried any project either yet (most of my sbt stuff publishes to private registries)

@Johnnei
Copy link
Contributor

Johnnei commented May 26, 2025

Tried a few things scapegoat-scala/sbt-scapegoat#227, but it does seem that the credentials don't work for Central Portal (I got confused with me changing the host in the last change).
I guess we need Sam to initiate the Central Portal migration for his namespaces (if he didn't already) and set new token in the env vars (which sbt still seems to use).

@scala-steward
Copy link
Contributor Author

Superseded by #962.

@scala-steward scala-steward deleted the update/sbt-ci-release-1.11.0 branch June 3, 2025 22:14
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.

4 participants