feat: add upgrade guide for StudioCMS v0.7.0

[Adammatthiesen]

This pull request adds upgrade documentation for StudioCMS v0.7.0 and makes a small adjustment to the v0.6.0 upgrade guide. The new v0.7.0 guide highlights important bug fixes and improvements, while the v0.6.0 guide has a minor sidebar update.

TODO Before Merging:

• Update package.json dependencies once new release it out

New upgrade guide for v0.7.0:

• Adds src/content/docs/en/guides/upgrade/version-guides/0-7-0.mdx with a summary of changes in v0.7.0, including migration to Satteri for internal markdown rendering, Windows path resolver fixes, a current user check in API search, and dependency updates.

Documentation sidebar updates:

• Removes the "NEW" badge from the sidebar configuration in the v0.6.0 upgrade guide (src/content/docs/en/guides/upgrade/version-guides/0-6-0.mdx).

Summary by CodeRabbit

• Documentation
  • Added a v0.7.0 upgrade guide covering Markdown rendering and parsing changes, Windows path resolution fixes, an API search current-user check, and dependency updates.
  • Clarified that page Markdown rendering continues to be handled by the plugin system.
  • Removed the “NEW” badge from the v0.6.0 guide’s sidebar metadata.
• Maintenance
  • Updated minimum supported versions for StudioCMS-related packages.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 1fd13da5-4c6e-4074-841f-f9ed6f8f3886

📥 Commits

Reviewing files that changed from the base of the PR and between 963511d and ef9c3e5.

⛔ Files ignored due to path filters: 1

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing: 1

• package.json

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The 0.7.0 upgrade guide was added with migration and fix notes. The 0.6.0 guide no longer displays the NEW sidebar badge. Package version ranges were updated.

Changes: Upgrade updates

Layer / File(s)	Summary
Version guide updates src/content/docs/en/guides/upgrade/version-guides/0-7-0.mdx, src/content/docs/en/guides/upgrade/version-guides/0-6-0.mdx	The 0.7.0 guide documents the Micromark-to-Satteri migration, Markdown-rendering scope, Windows path resolver fixes, an API search current-user check, and dependency updates. The 0.6.0 guide no longer displays the NEW sidebar badge.
Package version ranges package.json	Version ranges for StudioCMS packages, related @withstudiocms packages, effectify, and studiocms were updated.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Suggested reviewers: dreyfus92, louisescher

Merge Risk: ⚪ Minimal · up to ef9c3

The changes add upgrade documentation and update package ranges. No specific user-facing or workflow failure is established in the supplied evidence, so the PR appears mergeable subject to normal checks.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly and concisely describes the main change: adding the StudioCMS v0.7.0 upgrade guide.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

_{A rabbit reads the guides anew
And finds the badge has hopped away
Satteri joins the upgrade notes
New version ranges take their place
The rabbit thumps, then bounds away}

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

[studiocms-no-reply]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the tracking.ignoredKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
en/guides/upgrade/version-guides/0-6-0.mdx	Source changed, localizations will be marked as outdated.
en/guides/upgrade/version-guides/0-7-0.mdx	Localization added, will be marked as complete.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.