v0.4.0

[armanbilge]

https://github.com/typelevel/sbt-typelevel/milestone/1

This is more of a 0.1.0, except this is the next available version. In any case, what do we need to do to get here?

After the latest round of PRs merge I will probably migrate http4s-dom and feral.

todo

• steward support, merged but may need to be released?
  Add sbt-typelevel to sbtGitHubActionsModules scala-steward-org/scala-steward#2443
• bikeshed all the names. I'd love to make more stuff private, but I'm scared of sbt.
  Bikeshedding #80

[armanbilge]

Any feelings about cutting an 0.4.0-M1? In any case I'm going to migrate my projects.

[armanbilge]

Did three migrations, fixed a couple bugs. My builds are all slimmer and better :)

• Migrate to sbt-typelevel http4s/http4s-dom#77
• Migrate to sbt-typelevel bobcats#55
• Migrate to sbt-typelevel feral#142
• Migrate to sbt-typelevel spire#1138
• Migrate to sbt-typelevel and self-host http4s/sbt-http4s-org#120
• sbt-typelevel-ci-release doobie#1631
• Migrate to sbt-typelevel fs2#2791
• Adopt sbt-typelevel case-insensitive#208
• Migrate to sbt-typelevel jawn-fs2#296
• Adopt sbt-typelevel jawn#402
• Migrate to sbt-typelevel vault#349

[armanbilge]

I'm going to try cutting 0.4.0-M1, with the dreaded commit-and-tag push.

[armanbilge]

https://github.com/typelevel/sbt-typelevel/releases/tag/v0.4.0-M1

[armanbilge]

Confirmation that steward works with sbt-typelevel(-ci-release):

• Update scala-library, scala-reflect to 2.13.8 doobie#1634
• Update scala-library to 2.13.8 bobcats#59

[armanbilge]

Based on the discussion in #78 (comment) I think we should go to v0.4.0 ASAP, since it's not viable to adopt sbt-typelevel without support from steward.

If/when we have to break, we can go to 0.5.0, NBD.

[rossabaker]

Agreed.

[armanbilge]

https://github.com/typelevel/sbt-typelevel/releases/tag/v0.4.0