chore(main): release 0.1.0

[sht-bot]

🤖 I have created a release beep boop

0.1.0 (2026-01-17)

Features

• otel-collector: Add otel collector formula (db91cff)
• otel-collector: Add otel collector formula (efefef3)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Warning

Rate limit exceeded

@yordis has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 4 minutes and 20 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between c6454ba and ab2e647.

📒 Files selected for processing (2)

• .github/release-please-manifest.json
• CHANGELOG.md

Walkthrough

Version bumped from 0.0.1 to 0.1.0 in the release-please manifest. Initial CHANGELOG.md created documenting version 0.1.0 with two otel-collector formula feature additions.

Changes

Cohort / File(s)	Summary
Release Configuration .github/release-please-manifest.json	Version bump for root package from 0.0.1 to 0.1.0
Documentation CHANGELOG.md	New file created with 0.1.0 entry documenting two otel-collector formula features (commits db91cff, efefef3)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: add release-please #2 — Updates same .github/release-please-manifest.json file and adds CHANGELOG entry dependent on release-please infrastructure

Poem

🐰 Version hops from one to one,
A changelog begun, release fun!
With otel-collector now in sight,
0.1.0 shines so bright! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore(main): release 0.1.0' directly matches the changeset's primary purpose: releasing version 0.1.0 with version bumps and changelog updates.
Description check	✅ Passed	The description is related to the changeset, detailing the 0.1.0 release notes with specific features added and commit references.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Around line 8-9: The CHANGELOG contains duplicate entries for the same
feature—remove the merge commit entry with hash db91cff (the redundant "Add otel
collector formula" line) and keep only the actual feature commit entry efefef3;
edit the duplicate otel-collector line so the changelog lists a single entry for
commit efefef3 and ensure formatting remains consistent.

[sht-bot]

🤖 Created releases:

• v0.1.0

🌻