Matthias Kurz
Matthias Kurz
> This will hopefully get everything over the tipping point and we can forget about scala-xml 1.x and this issue for good. scala-parser-combinators like: hold my beer :wink:
> Either way the ball is sort of rolling, so how do we think it's best to proceed, and how can I help? Maybe get sbt 1.7.4 out fast out...
And what about the enter key, 13 (cr) vs 10 (lf)?
I get someting similiar running sbt 1.7.0-M2 inside a Ubuntu 22.04 virtual machine on my Macbook Pro M1: ```sh $ sbt --client /home/mkurz/.sdkman/candidates/sbt/1.7.0-M2/sbt: line 222: /home/mkurz/.cache/sbt/boot/sbtn/1.4.7/sbtn: cannot execute binary file:...
Yeah, that's why probably.
> Could you ask the lombok project if there are any arguments or system properties that control recognition of the config file? FYI, I just opened a pull request in...
I am pretty sure you can solve this with the `filter-by-commitish` config. I wrote a little guide how to make things work, specially how to see and update the `target_commitish`...
+1 We have almost the exact use case like in the original comment. @jetersen Would it be possible to iterate over the secrets (like `secrets.*`) ourselves and mask secrets instead...
@jetersen I ike that idea with replacers. So basically this would be whitelisting env vars. Maybe just call it `environment-whitelist`? Just an idea, I am fine with whatever naming.
More people experienced this: https://github.com/sbt/sbt-ci-release/issues/223