docs: migration from Kratos 0.10.0

[hperl]

Summary by CodeRabbit

• Documentation
  • Updated the upgrade guide with new information about v0.10.0 Authenticator Assurance Level (AAL) changes in sessions. Clarified that upgrading requires reissuing sessions to observe higher AAL when multi-factor methods are used.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation update to the upgrade guide with formatting adjustments to an existing section, whitespace normalization, and a new section documenting that the Authenticator Assurance Level (AAL) is now included in sessions starting from v0.10.0.

Changes

Cohort / File(s)	Summary
Upgrade Guide Documentation docs/kratos/guides/upgrade.mdx	Adjusted line wrapping in "Review breaking changes" section, normalized trailing whitespace in "v0.7 Changed cookie behavior" section, and added new "v0.10.0 Authenticator assurance level (AAL) in session" section documenting AAL inclusion in sessions and session reissuance requirements.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided by the author, but the template requires a description explaining changes and including related issue references.	Add a pull request description following the template, explaining the changes made to the upgrade guide and confirming the checklist items.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'docs: migration from Kratos 0.10.0' is specific and relates to the documentation update about Kratos 0.10.0 migration, matching the upgrade guide changes.
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 hperl/kratos-v0.9-upgrade

---

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

[coderabbitai]

🧹 Nitpick comments (1)

docs/kratos/guides/upgrade.mdx (1)

34-34: Consider clarifying the migration action required.

The phrase "sessions need to be reissued to observe a higher AAL due to multi-factor methods" could be more explicit about what users need to do. Consider rephrasing for clarity, such as: "Existing sessions must be reissued (users must re-authenticate) for the AAL to reflect their multi-factor authentication methods."

Additionally, like the v0.7 section above, consider adding links to relevant documentation or example implementations to help users complete the migration.

📝 Suggested rewording for clarity

-Since [Ory Kratos v0.10.0](https://github.com/ory/kratos/blob/v0.10.0/CHANGELOG.md#breaking-changes), the AAL is part of the
-session. When upgrading, sessions need to be reissued to observe a higher AAL due to multi-factor methods.
+Since [Ory Kratos v0.10.0](https://github.com/ory/kratos/blob/v0.10.0/CHANGELOG.md#breaking-changes), the AAL is included in the
+session. When upgrading, existing sessions must be reissued (users must re-authenticate) for the AAL to reflect their multi-factor authentication methods.

🤖 Prompt for AI Agents

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

In `@docs/kratos/guides/upgrade.mdx` at line 34, Replace the vague sentence
"sessions need to be reissued to observe a higher AAL due to multi-factor
methods" with an explicit migration instruction such as "Existing sessions must
be reissued (users must re-authenticate) so their session's AAL reflects newly
enrolled multi-factor authentication methods," and add links to the relevant
Kratos re-authentication/session-management docs or an example implementation
(matching the style used in the v0.7 section) to help users perform the
migration; update the surrounding text in the same paragraph to mention whether
reissue is automatic or requires user action and where to find sample code.

🤖 Prompt for all review comments with AI agents

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

Nitpick comments:
In `@docs/kratos/guides/upgrade.mdx`:
- Line 34: Replace the vague sentence "sessions need to be reissued to observe a
higher AAL due to multi-factor methods" with an explicit migration instruction
such as "Existing sessions must be reissued (users must re-authenticate) so
their session's AAL reflects newly enrolled multi-factor authentication
methods," and add links to the relevant Kratos
re-authentication/session-management docs or an example implementation (matching
the style used in the v0.7 section) to help users perform the migration; update
the surrounding text in the same paragraph to mention whether reissue is
automatic or requires user action and where to find sample code.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3d1a87ce-bc7b-41c0-888a-1bda463f43aa

📥 Commits

Reviewing files that changed from the base of the PR and between 0fa5879 and 3a7a737.

📒 Files selected for processing (1)

• docs/kratos/guides/upgrade.mdx

[Copilot]

Pull request overview

Updates the Ory Kratos upgrade guide to better document migration considerations around Kratos v0.10.0, while also cleaning up some Markdown formatting.

Changes:

• Reformat the “Review breaking changes” list item for cleaner Markdown rendering.
• Remove an unnecessary hard line break in the v0.7 cookie behavior section.
• Add a new v0.10.0 note explaining that AAL is now part of the session and that sessions must be reissued after upgrade.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[jonas-jonas]

perfect, thanks