I can sbt +publish to stage and then sbt bintrayRelease to publish all the staged stuff once I'm happy
no more manual zip crap
because that was a huge barrier to me contributing effectively
once I get releases from ci set up, I'll also look at scala-steward
Sorry for my ignorance but do you think it is practicable that you setup the actions on you streamz fork and once they are working I "copy" them to this repo?
I'm not sure. The sbt-github-actions generated setup seems to work just fine. The main part I'm not sure of is the secrets management.
But yeah, to test that I think I can make a fork (I'll just change the package name or something to not conflict as I test)
I was mainly asking because that would avoid creating an organization and moving the repo. But if you prefer having more permission for this repo (via an organization) instead of working on a fork for setting up actions I'm happy to create one.
Whatever you prefer
ok, then let's try with a fork first and if this doesn't work I'll create an org.
k. I'll DM you the secrets to add once I get that far
maybe this weekend if I have time to work on it
hello, and thank you for the library! How do I include v0.13-RC4 into my sbt project? I added resolvers += Resolver.bintrayRepo("streamz", "maven")
and "com.github.krasserm" %% "streamz-converter" % "0.13-RC4"
but I get "Unresolved dependencies" error
@vasily802 Try using ThisBuild / resolvers += ...
if you have a multi-module project, then doing resolvers += just adds it to the synthetic "root" project scope which probably isn't the one you have your code in