feat/codeowners

[matheusfillipe]

• 0.3.1
• add codeowners

Summary by CodeRabbit

• Chores
  • Version bumped to 0.3.1
  • Updated repository configuration

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 36f3d0c6-9242-4a5a-8077-91741bb417f1

📥 Commits

Reviewing files that changed from the base of the PR and between 2257f1c and cdb4471.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• .github/CODEOWNERS
• package.json

---

📝 Walkthrough

Walkthrough

Repository ownership is assigned in CODEOWNERS to two users, and the package version is incremented from 0.3.0 to 0.3.1 in preparation for a minor release.

Changes

Repository Maintenance

Layer / File(s)	Summary
Ownership and version updates .github/CODEOWNERS, package.json	CODEOWNERS assigns repository root (*) ownership to two users; package version bumped from 0.3.0 to 0.3.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version bump and owners set,
The maintenance dance, a minor bet!
From 0.3.0 to point one,
With guardians named—the work is done!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'feat/codeowners' is partially related to the changeset but uses a branch naming convention rather than a clear, descriptive summary of the actual changes.	Revise the title to be more descriptive, such as 'Add CODEOWNERS file to assign repository ownership' or 'Bump version to 0.3.1 and add CODEOWNERS'. Avoid using branch names as PR titles.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/codeowners

---

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.}