Escape the giterate template dollar sign.

Update tzdb and locales.

Specify runner dialect explicitly.

Nix flake update, using flake-compat.

Template version bump.

Setting version to 0.3.5-SNAPSHOT

Setting version to 0.3.4

No blaze server for 0.23.13 yet. ...

Or maybe we just need separate versions, unsure.

Default props version bump.

Setting version to 0.3.4-SNAPSHOT

Setting version to 0.3.3

Typo fix in tapir zio http4s server.

Version bump in template.

Setting version to 0.3.3-SNAPSHOT

Setting version to 0.3.2

Rename the tapir zio server. ...

Upstream change.

Template update.

Setting version to 0.3.2-SNAPSHOT

Setting version to 0.3.1

Set Scala 3 as default.

Setting version to 0.3.1-SNAPSHOT

Setting version to 0.3.0

ZIO, http4s and Tapir update.

Scala and sbt-native-packager version bump.

Update scala3 version.

ZIO update to 2.0.0-RC6

ScalaJS 1.10.0

Put slick projection back. ...

The overhead of keeping separate database configuration for journal and
projection is not worth it.

Yes, technically these are and should be two separate databases. Not for
the small services I write, though - and even if they would be, which
makes sense, it would still be easier to use the same method of
cofiguration for both.

Maybe drop Slick from the journal as well? Well, the official
akka-persistence-jdbc is using it, so I guess not, unless I want to
replace the JDBC altogether.

Replace slick project with jdbc. ...

Aparently slick projection is something not to be used according to the
akka documentation, only for migration from slick ReadProcessors.

Working version of akka-projection with slick.