Bump base version to 3.4

[armanbilge]

Best practice is to bump the base version in the PR that makes the changes that require the bump in the next release :)

Unfortunately we cannot enforce this automatically since we are lacking a good way to check forward-binary-compatibility.

[joroKr21]

How can we bump the base version before it's released? 🤔

[armanbilge]

You literally just bump it, exactly like I did in this PR :)

For example, in the Cats Effect PR that introduced the polling system, we bumped the base version to 3.6. But we have not yet released Cats Effect v3.6.0.

• Polling system cats-effect#3332

[joroKr21]

Best practice is to bump the base version in the PR that makes the changes that require the bump in the next release :)

The moment I realise if a minor version bump is needed is when GitHub generates the release notes for me 😝

[armanbilge]

Well, it depends what versioning strategy you are following. Under the "strict best practice" basically anything that is not a bug fix / optimization warrants a bump of the minor version.

[joroKr21]

For example, in the Cats Effect PR that introduced the polling system, we bumped the base version to 3.6. But we have not yet released Cats Effect v3.6.0.

Dunno, it sounds very confusing. I guess the name doesn't really speak to me. When I see tlBaseVersion it sounds like the previous release. But it should in fact be the current one. I will try to remember 👍

[joroKr21]

Well, it depends what versioning strategy you are following. Under the "strict best practice" basically anything that is not a bug fix / optimization warrants a bump of the minor version.

In this case it was Scala 3.2 -> 3.3 bump

[armanbilge]

Further reading: https://typelevel.org/sbt-typelevel/faq.html#what-is-a-base-version-anyway