chore: v0.2.0-next

[feloy]

No description provided.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[coderabbitai]

📝 Walkthrough

Walkthrough

The application version identifier is updated from 0.1.0-next to 0.2.0-next in the version file. This is a simple version string modification without any logic or control flow changes.

Changes

Cohort / File(s)	Summary
Version Update pkg/version/version.go	Updated exported Version string constant from "0.1.0-next" to "0.2.0-next".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided, making it impossible to assess whether any description relates to the changeset.	Add a brief description explaining the purpose of the version bump, such as release notes or feature readiness.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title 'chore: v0.2.0-next' directly and specifically describes the main change: updating the version identifier from 0.1.0-next to 0.2.0-next.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[benoitf]

question: should the bump PR be part of the release workflow ?

[feloy]

question: should the bump PR be part of the release workflow ?

yes: #123