search

polystat / polystat-cli

MIT License
5 stars 3 forks source link

Update dependency com.github.sbt:sbt-release to v1.4.0 - autoclosed #40

Closed renovate[bot] closed 1 month ago

renovate[bot] commented 9 months ago

This PR contains the following updates:

Package Type Update Change
com.github.sbt:sbt-release plugin minor 1.1.0 -> 1.4.0

Release Notes

sbt/sbt-release (com.github.sbt:sbt-release) ### [`v1.4.0`](https://redirect.github.com/sbt/sbt-release/releases/tag/v1.4.0): 1.4.0 [Compare Source](https://redirect.github.com/sbt/sbt-release/compare/v1.3.0...v1.4.0) #### Breaking Change: Prerelease version increments Prior to sbt-release 1.4.0, if a prerelease version (for example `1.0.0-RC1`) is incremented, the prerelease part `RC1` is dropped, so `1.0.0-RC1` was incremented to `1.0.0`. By default, sbt-release 1.4.0 increments prerelease versions by default, if it ends in a number. In other words, `1.0.0-RC1` is incremented to `1.0.0-RC2`. To restore the previous behavior, you can set the following setting: ```scala releaseVersionBump := sbtrelease.Version.Bump.NextStable ``` This was contributed by [@​Andrapyre](https://redirect.github.com/Andrapyre) in [https://github.com/sbt/sbt-release/pull/397](https://redirect.github.com/sbt/sbt-release/pull/397) #### Updates - Update specs2-core to 4.20.4 by [@​scala-steward-bot](https://redirect.github.com/scala-steward-bot) in [https://github.com/sbt/sbt-release/pull/399](https://redirect.github.com/sbt/sbt-release/pull/399) **Full Changelog**: https://github.com/sbt/sbt-release/compare/v1.3.0...v1.4.0

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.

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

yegor256 commented 9 months ago

@rultor please, try to merge, since 5 checks have passed

rultor commented 9 months ago

@rultor please, try to merge, since 5 checks have passed

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

rultor commented 9 months ago

@rultor please, try to merge, since 5 checks have passed

@renovate[bot] @yegor256 Oops, I failed. You can see the full log here (spent 8s)

+ set -e
+ set -o pipefail
++ dirname ./run.sh
+ cd .
+ echo 1634175
+ echo '2.0-SNAPSHOT BUILD'
2.0-SNAPSHOT BUILD
+ date
Thu Jan 18 05:43:24 AM CET 2024
+ uptime
 05:43:24 up 126 days,  9:57,  0 users,  load average: 0.08, 0.08, 0.08
+ cat
com.rultor.spi.Profile: There is no 'merge' section in .rultor.yml for branch master in repo polystat/polystat-cli
    at com.rultor.agents.req.StartsRequest.docker(StartsRequest.java:350)
    at com.rultor.agents.req.StartsRequest.vars(StartsRequest.java:255)
    at com.rultor.agents.req.StartsRequest.script(StartsRequest.java:148)
    at com.rultor.agents.req.StartsRequest.process(StartsRequest.java:109)
    at com.rultor.agents.AbstractAgent.execute(AbstractAgent.java:75)
    at com.rultor.spi.Agent.execute(Agent.java:84)
    at com.rultor.agents.VerboseAgent.execute(VerboseAgent.java:62)
    at com.rultor.Routine.process(Routine.java:202)
    at com.rultor.Routine.unsafe_aroundBody0(Routine.java:180)
    at com.rultor.Routine.run(Routine.java:1)
    at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:179)
    at com.jcabi.aspects.aj.MethodInterrupter.wrap(MethodInterrupter.java:108)
    at com.rultor.Routine.unsafe(Routine.java:175)
    at com.rultor.Routine.run(Routine.java:142)
    at com.jcabi.log.VerboseRunnable.run(VerboseRunnable.java:190)
    at com.jcabi.aspects.aj.MethodScheduler.lambda./run.sh(MethodScheduler.java:194)
    at java.base/java.util.concurrent.Executors.call(Executors.java:539)
    at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
    at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.run(ScheduledThreadPoolExecutor.java:305)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
    at java.base/java.util.concurrent.ThreadPoolExecutor.run(ThreadPoolExecutor.java:635)
    at com.jcabi.log.VerboseThreads.run(VerboseThreads.java:222)
    at java.base/java.lang.Thread.run(Thread.java:833)

+ exit -1
'cid' file is absent, most probably the Docker container wasn't started correctly