chore: release v0.4.1

[Koosha-Owji]

Explain your changes

Release v0.4.1 - bumps version in package.json and updates CHANGELOG.md.

Checklist

• I have read the “Pull requests” section in the contributing guidelines.
• I agree to the terms within the code of conduct.

🛟 If you need help, consider asking for advice over in the Kinde community.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6b91270d-7bfb-47a2-ad26-5fb7ab795567

📥 Commits

Reviewing files that changed from the base of the PR and between 1eae5ff and 80665fe.

📒 Files selected for processing (1)

• CHANGELOG.md

✅ Files skipped from review due to trivial changes (1)

• CHANGELOG.md

---

Walkthrough

Added a new top-level changelog entry 0.4.1...main with chore items about dependency file handling and a contributors list crediting Andre Selton and Daniel Rivers.

Changes

Cohort / File(s)	Summary
Changelog Update CHANGELOG.md	Inserted new version section 0.4.1...main (compare link) with three chore items: ignore renovate.json, remove package-lock.json, update CODEOWNERS for dependency files; added “❤️ Contributors” listing Andre Selton and Daniel Rivers.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: release v0.4.1' clearly and directly summarizes the main change—releasing version 0.4.1, which aligns with the CHANGELOG.md update and version bump described in the PR.
Description check	✅ Passed	The description is directly related to the changeset, explaining that it releases v0.4.1 by bumping the version in package.json and updating CHANGELOG.md, which matches the actual changes made.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore-release-v0.4.1

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

CHANGELOG.md (1)

6-6: Prefer immutable compare ranges for release entries.

Using ...main in a versioned release section can drift as new commits land. Pinning to tags keeps changelog history stable and auditable.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` at line 6, Replace the unstable compare URL "[compare
changes](https://github.com/kinde-oss/jwt-validator/compare/0.4.0...main)" with
a pinned tag range so the release entry is immutable; update the link to use the
prior tag and the release tag (e.g., "0.4.0...0.4.1") or the exact tag for the
new release instead of "main" in the CHANGELOG.md entry so the compare range
remains stable and auditable.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Around line 4-7: Update the changelog header that currently reads
"0.4.0...main" to match the PR release target by changing it to "0.4.1...main"
in CHANGELOG.md (look for the exact string "0.4.0...main"); ensure the compare
link and any nearby version references match the new version label so the
release notes are consistent with v0.4.1.

---

Nitpick comments:
In `@CHANGELOG.md`:
- Line 6: Replace the unstable compare URL "[compare
changes](https://github.com/kinde-oss/jwt-validator/compare/0.4.0...main)" with
a pinned tag range so the release entry is immutable; update the link to use the
prior tag and the release tag (e.g., "0.4.0...0.4.1") or the exact tag for the
new release instead of "main" in the CHANGELOG.md entry so the compare range
remains stable and auditable.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c3910f97-3590-41d9-bb8d-66544cb01e53

📥 Commits

Reviewing files that changed from the base of the PR and between 0b3996a and 1eae5ff.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• CHANGELOG.md