Skip to content
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

Update sbt-ci-release to 1.5.11 & sbt-ghpages to 0.7.0 #1705

Merged
merged 2 commits into from
Dec 15, 2022

Conversation

scala-center-steward[bot]
Copy link
Contributor

Updates com.github.sbt:sbt-ci-release from 1.5.10 to 1.5.11.
GitHub Release Notes - Version Diff

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!

Files still referring to the old version number

The following files still refer to the old version number (1.5.10).
You might want to review and update them manually.

docs/developers/tutorial.md
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 = "@monthly" },
  dependency = { groupId = "com.github.sbt", artifactId = "sbt-ci-release" }
}]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

@bjaglin
Copy link
Collaborator

bjaglin commented Dec 15, 2022

java.lang.RuntimeException: Some keys were defined with the same name but different types: 'gitReader' (com.typesafe.sbt.git.ReadableGit, com.github.sbt.git.ReadableGit), 'gitRunner' (sbt.Task[com.typesafe.sbt.git.GitRunner], sbt.Task[com.github.sbt.git.GitRunner])

@bjaglin
Copy link
Collaborator

bjaglin commented Dec 15, 2022

https://github.com/sbt/sbt-ci-release/pull/236/files#diff-8fd74420ca55aa91d4c53775d2a55a999c405b5a4fafeaf73b7f0ef83e1f3b0cL7

sbt/sbt-git#218

On main

sbt:project> whatDependsOn com.typesafe.sbt\ sbt-git
[info] com.typesafe.sbt:sbt-git:1.0.2
[info]   +-com.github.sbt:sbt-ci-release:1.5.10
[info]   | +-default:project:0.1.0-SNAPSHOT
[info]   | 
[info]   +-com.typesafe.sbt:sbt-ghpages:0.6.3
[info]     +-default:project:0.1.0-SNAPSHOT
[info]     
[info] com.typesafe.sbt:sbt-git:0.9.3 (evicted by: 1.0.2)
[info]   +-com.typesafe.sbt:sbt-ghpages:0.6.3
[info]     +-default:project:0.1.0-SNAPSHOT
[info]     

@bjaglin bjaglin force-pushed the update/sbt-ci-release-1.5.11 branch from 7a58254 to 1654fb5 Compare December 15, 2022 21:55
@bjaglin bjaglin changed the title Update sbt-ci-release to 1.5.11 Update sbt-ci-release to 1.5.11 & sbt-ghpages to 0.7.0 Dec 15, 2022
@bjaglin bjaglin merged commit 1d28ed0 into main Dec 15, 2022
@bjaglin
Copy link
Collaborator

bjaglin commented Dec 15, 2022

It looks like this broke publishing

[info] Welcome to scalafix 0.10.4+55-1d28ed0c-SNAPSHOT
Running ci-release.
  branch=refs/heads/main
gpg (GnuPG) 2.2.27
I/O error Pipe closed for process: <input stream>
java.io.IOException: Pipe closed
	at java.io.PipedInputStream.checkStateForReceive(PipedInputStream.java:260)
	at java.io.PipedInputStream.awaitSpace(PipedInputStream.java:268)
	at java.io.PipedInputStream.receive(PipedInputStream.java:231)
	at java.io.PipedOutputStream.write(PipedOutputStream.java:149)
	at scala.sys.process.BasicIO$.loop$1(BasicIO.scala:240)
	at scala.sys.process.BasicIO$.transferFullyImpl(BasicIO.scala:246)
	at scala.sys.process.BasicIO$.transferFully(BasicIO.scala:227)
	at scala.sys.process.ProcessImpl$PipeThread.runloop(ProcessImpl.scala:170)
	at scala.sys.process.ProcessImpl$PipeSource.run(ProcessImpl.scala:188)
java.lang.RuntimeException: base64: invalid input
	at com.geirsson.PipeFail$PipeFailOps.$hash$bar$bang(PipeFail.scala:28)
	at com.geirsson.CiReleasePlugin$.setupGpg(CiReleasePlugin.scala:96)
	at com.geirsson.CiReleasePlugin$.$anonfun$globalSettings$4(CiReleasePlugin.scala:144)
	at sbt.Command$.$anonfun$command$2(Command.scala:97)
	at sbt.Command$.process(Command.scala:189)
	at sbt.MainLoop$.$anonfun$processCommand$5(MainLoop.scala:245)
	at scala.Option.getOrElse(Option.scala:189)
	at sbt.MainLoop$.process$1(MainLoop.scala:245)
	at sbt.MainLoop$.processCommand(MainLoop.scala:276)
	at sbt.MainLoop$.$anonfun$next$5(MainLoop.scala:163)
	at sbt.State$StateOpsImpl$.runCmd$1(State.scala:289)
	at sbt.State$StateOpsImpl$.process$extension(State.scala:325)
	at sbt.MainLoop$.$anonfun$next$4(MainLoop.scala:163)
	at sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:23)
	at sbt.MainLoop$.next(MainLoop.scala:163)
	at sbt.MainLoop$.run(MainLoop.scala:144)
	at sbt.MainLoop$.$anonfun$runWithNewLog$1(MainLoop.scala:119)
	at sbt.io.Using.apply(Using.scala:27)
	at sbt.MainLoop$.runWithNewLog(MainLoop.scala:112)
	at sbt.MainLoop$.runAndClearLast(MainLoop.scala:66)
	at sbt.MainLoop$.runLoggedLoop(MainLoop.scala:51)
	at sbt.MainLoop$.runLogged(MainLoop.scala:42)
	at sbt.StandardMain$.runManaged(Main.scala:223)
	at sbt.xMain$.$anonfun$run$11(Main.scala:133)
	at sbt.internal.util.Terminal$.withStreams(Terminal.scala:389)
	at sbt.xMain$.withStreams$1(Main.scala:87)
	at sbt.xMain$.run(Main.scala:121)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at sbt.internal.XMainConfiguration.run(XMainConfiguration.java:57)
	at sbt.xMain.run(Main.scala:46)
	at xsbt.boot.Launch$.$anonfun$run$1(Launch.scala:149)
	at xsbt.boot.Launch$.withContextLoader(Launch.scala:176)
	at xsbt.boot.Launch$.run(Launch.scala:149)
	at xsbt.boot.Launch$.$anonfun$apply$1(Launch.scala:44)
	at xsbt.boot.Launch$.launch(Launch.scala:159)
	at xsbt.boot.Launch$.apply(Launch.scala:44)
	at xsbt.boot.Launch$.apply(Launch.scala:21)
	at xsbt.boot.Boot$.runImpl(Boot.scala:78)
	at xsbt.boot.Boot$.run(Boot.scala:73)
	at xsbt.boot.Boot$.main(Boot.scala:21)
	at xsbt.boot.Boot.main(Boot.scala)
Caused by: java.lang.RuntimeException: Nonzero exit value: 1
	at scala.sys.package$.error(package.scala:30)
	at scala.sys.process.ProcessBuilderImpl$AbstractBuilder.slurp(ProcessBuilderImpl.scala:138)
	at scala.sys.process.ProcessBuilderImpl$AbstractBuilder.$bang$bang(ProcessBuilderImpl.scala:109)
	at com.geirsson.PipeFail$PipeFailOps.$anonfun$$hash$bar$bang$1(PipeFail.scala:22)
	at scala.util.Try$.apply(Try.scala:213)
	at com.geirsson.PipeFail$PipeFailOps.$hash$bar$bang(PipeFail.scala:22)
	... 43 more
[error] base64: invalid input

Might be related to sbt/sbt-ci-release#238, as we see similar, non-fatal errors in the previous successful build from today:

 Running ci-release.
  branch=refs/heads/main
gpg (GnuPG) 2.2.27
gpg: directory '/home/runner/.gnupg' created
gpg: keybox '/home/runner/.gnupg/pubring.kbx' created
base64: invalid input
gpg: no valid OpenPGP data found.
gpg: read_block: read error: Invalid packet
gpg: import from '[stdin]' failed: Invalid keyring
gpg: Total number processed: 0
No tag push, publishing SNAPSHOT

@bjaglin
Copy link
Collaborator

bjaglin commented Dec 15, 2022

Interestingly, runs from a month ago did not have this error

[info] Welcome to scalafix 0.10.4+42-491deb22-SNAPSHOT
Running ci-release.
  branch=refs/heads/main
gpg (GnuPG) 1.4.23
gpg: directory `/home/runner/.gnupg' created
gpg: can't open `/usr/local/share/gnupg/options.skel': No such file or directory
gpg: keyring `/home/runner/.gnupg/secring.gpg' created
gpg: keyring `/home/runner/.gnupg/pubring.gpg' created
gpg: key D4A5B6E7: secret key imported
gpg: /home/runner/.gnupg/trustdb.gpg: trustdb created
gpg: key D4A5B6E7: public key "funsuite 2 bot <***>" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
gpg:       secret keys read: 1
No tag push, publishing SNAPSHOT

... and it seems that the PGP_* organization secrets were updated yesterday 🤔

@bjaglin
Copy link
Collaborator

bjaglin commented Dec 15, 2022

@adpi2 does that ring a bell? thanks!

@julienrf
Copy link
Contributor

It might be caused by recent changes we did on the GitHub secrets for publishing (they are now handled at the organization-level instead of the repo-level). They were not properly set and I had to reset them a couple of days ago. It seems that publishing works fine now? See https://github.com/scalacenter/scalafix/actions/runs/3736411213/jobs/6340689713

@julienrf julienrf deleted the update/sbt-ci-release-1.5.11 branch December 20, 2022 14:45
@bjaglin
Copy link
Collaborator

bjaglin commented Dec 20, 2022

It seems that publishing works fine now?

It does indeed, I didn't retry after the initial failure a couple of days ago. Thanks for checking!

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.

2 participants