Skip to content

chore: release v0.10.0#117

Open
Koosha-Owji wants to merge 1 commit into
mainfrom
release/v0.10.0
Open

chore: release v0.10.0#117
Koosha-Owji wants to merge 1 commit into
mainfrom
release/v0.10.0

Conversation

@Koosha-Owji
Copy link
Copy Markdown
Contributor

Explain your changes

version bump and changelog update

Checklist

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

@Koosha-Owji Koosha-Owji requested review from a team as code owners May 29, 2026 04:43
@codecov
Copy link
Copy Markdown

codecov Bot commented May 29, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 29, 2026

Review Change Stack

Walkthrough

A new changelog entry for release 0.9.0...main has been added to the top of CHANGELOG.md, documenting bug fixes, chore updates including dependency and tooling version alignment, CI/workspace maintenance, and contributor attribution.

Changes

Release Documentation

Layer / File(s) Summary
0.9.0 changelog entry
CHANGELOG.md
New release section with compare link, categorized Fixes and Chore entries capturing dependency/tooling updates and CI maintenance, followed by a Contributors list.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change—a version release update for v0.10.0 with corresponding changelog updates.
Description check ✅ Passed The description is directly related to the changeset, specifying version bump and changelog update as the primary changes.
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 release/v0.10.0

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

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

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CHANGELOG.md`:
- Around line 34-35: The changelog currently lists personal email addresses for
contributors "Koosha Owji <koosha.owji@gmail.com>" and "Andre Selton
<andre@kinde.com>"; replace those email-containing entries with their GitHub
handles (or the same format used in other entries) so no PII is published, e.g.
change the two lines referencing Koosha Owji and Andre Selton to their GitHub
usernames in the contributors list.
- Around line 4-7: The release header in CHANGELOG.md currently reads "##
0.9.0...main" which mismatches the PR target v0.10.0; update the header and its
compare link to reference 0.10.0 (e.g., change the section title "##
0.9.0...main" to "## 0.10.0...main" and update the compare URL from
/compare/0.9.0...main to /compare/0.10.0...main) so the changelog reflects the
correct release version.
🪄 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: 3bc63b30-00bf-4cae-90e9-9037439740fc

📥 Commits

Reviewing files that changed from the base of the PR and between d5edabb and 31ac71d.

⛔ Files ignored due to path filters (2)
  • package-lock.json is excluded by !**/package-lock.json, !**/*.json
  • package.json is excluded by !**/*.json
📒 Files selected for processing (1)
  • CHANGELOG.md

Comment thread CHANGELOG.md
Comment on lines +4 to +7
## 0.9.0...main

[compare changes](https://github.com/kinde-oss/infrastructure/compare/0.9.0...main)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Release version label is inconsistent with the PR target version.

The PR is for release v0.10.0, but this section is labeled 0.9.0...main. This can publish incorrect release notes for the wrong version.

Suggested fix
-## 0.9.0...main
+## 0.10.0...main

-[compare changes](https://github.com/kinde-oss/infrastructure/compare/0.9.0...main)
+[compare changes](https://github.com/kinde-oss/infrastructure/compare/0.10.0...main)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## 0.9.0...main
[compare changes](https://github.com/kinde-oss/infrastructure/compare/0.9.0...main)
## 0.10.0...main
[compare changes](https://github.com/kinde-oss/infrastructure/compare/0.10.0...main)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` around lines 4 - 7, The release header in CHANGELOG.md
currently reads "## 0.9.0...main" which mismatches the PR target v0.10.0; update
the header and its compare link to reference 0.10.0 (e.g., change the section
title "## 0.9.0...main" to "## 0.10.0...main" and update the compare URL from
/compare/0.9.0...main to /compare/0.10.0...main) so the changelog reflects the
correct release version.

Comment thread CHANGELOG.md
Comment on lines +34 to +35
- Koosha Owji <koosha.owji@gmail.com>
- Andre Selton <andre@kinde.com>
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Avoid publishing personal email addresses in contributors list.

These lines expose PII in a public changelog. Prefer GitHub handles (as used in prior entries) instead of raw emails.

Suggested fix
-- Koosha Owji <koosha.owji@gmail.com>
-- Andre Selton <andre@kinde.com>
+- Koosha Owji ([`@Koosha-Owji`](https://github.com/Koosha-Owji))
+- Andre Selton ([`@andreselton`](https://github.com/andreselton))
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- Koosha Owji <koosha.owji@gmail.com>
- Andre Selton <andre@kinde.com>
- Koosha Owji ([`@Koosha-Owji`](https://github.com/Koosha-Owji))
- Andre Selton ([`@andreselton`](https://github.com/andreselton))
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` around lines 34 - 35, The changelog currently lists personal
email addresses for contributors "Koosha Owji <koosha.owji@gmail.com>" and
"Andre Selton <andre@kinde.com>"; replace those email-containing entries with
their GitHub handles (or the same format used in other entries) so no PII is
published, e.g. change the two lines referencing Koosha Owji and Andre Selton to
their GitHub usernames in the contributors list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant