add beta.20 guide#142
Conversation
WalkthroughThis update removes the "NEW" badge from the upgrade guide for version 0.1.0-beta.19, adds a new upgrade guide for version 0.1.0-beta.20 with a "NEW" badge and content about bug fixes and breaking changes, and updates the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Docs
participant StudioCMS
User->>Docs: Access upgrade guide for 0.1.0-beta-20
Docs->>StudioCMS: Reference new subproject commit
Docs-->>User: Display guide with bug fix and breaking change note
Estimated code review effort1 (~3 minutes) Possibly related PRs
Suggested reviewers
Poem
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-20.mdx (3)
21-21: Fix article misuse & reduce repetition in bug-fix sentence“a unavailable” → “an unavailable”, and “First time setup” is repeated three times.
- - Fixed First time setup routes that used a unavailable middleware feature during first time setup, causing the first time setup to fail. + - Fixed first-time setup routes that used an unavailable middleware feature, causing the initial setup to fail.
23-25: Clarify breaking-change note & add forward referenceConsider adding a link to the beta 16 release notes (or upgrade guide) so readers can easily review the original hashing-algorithm change.
-Please note that in `beta.16` we introduced a breaking change with the password hashing algorithm. +In `beta.16`, we introduced a breaking change to the password-hashing algorithm ([see details](../0-1-0-beta-16)).
27-32: Remove or use orphaned link referencesThe footnote references (
[config-doc],[image-service], etc.) are declared but never used in this document, which creates dead weight and potential confusion for translators and link checkers.If they are not needed here, delete lines 27-32; otherwise, add in-text links that make use of them.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-19.mdx(0 hunks)src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-20.mdx(1 hunks)studiocms(1 hunks)
🧠 Learnings (3)
📓 Common learnings
Learnt from: ArmandPhilippot
PR: withstudiocms/docs#140
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-19.mdx:24-24
Timestamp: 2025-07-21T12:16:32.374Z
Learning: In the withstudiocms/docs repository, documentation URLs in the package-catalog may maintain legacy path names for stability and consistency across language versions, even when the actual package names have been updated. Always verify that corresponding files exist before flagging URLs as broken.
studiocms (1)
Learnt from: ArmandPhilippot
PR: #140
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-19.mdx:24-24
Timestamp: 2025-07-21T12:16:32.374Z
Learning: In the withstudiocms/docs repository, documentation URLs in the package-catalog may maintain legacy path names for stability and consistency across language versions, even when the actual package names have been updated. Always verify that corresponding files exist before flagging URLs as broken.
src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-20.mdx (1)
Learnt from: ArmandPhilippot
PR: #140
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-19.mdx:24-24
Timestamp: 2025-07-21T12:16:32.374Z
Learning: In the withstudiocms/docs repository, documentation URLs in the package-catalog may maintain legacy path names for stability and consistency across language versions, even when the actual package names have been updated. Always verify that corresponding files exist before flagging URLs as broken.
💤 Files with no reviewable changes (1)
- src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-19.mdx
🧰 Additional context used
🧠 Learnings (3)
📓 Common learnings
Learnt from: ArmandPhilippot
PR: withstudiocms/docs#140
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-19.mdx:24-24
Timestamp: 2025-07-21T12:16:32.374Z
Learning: In the withstudiocms/docs repository, documentation URLs in the package-catalog may maintain legacy path names for stability and consistency across language versions, even when the actual package names have been updated. Always verify that corresponding files exist before flagging URLs as broken.
studiocms (1)
Learnt from: ArmandPhilippot
PR: #140
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-19.mdx:24-24
Timestamp: 2025-07-21T12:16:32.374Z
Learning: In the withstudiocms/docs repository, documentation URLs in the package-catalog may maintain legacy path names for stability and consistency across language versions, even when the actual package names have been updated. Always verify that corresponding files exist before flagging URLs as broken.
src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-20.mdx (1)
Learnt from: ArmandPhilippot
PR: #140
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-19.mdx:24-24
Timestamp: 2025-07-21T12:16:32.374Z
Learning: In the withstudiocms/docs repository, documentation URLs in the package-catalog may maintain legacy path names for stability and consistency across language versions, even when the actual package names have been updated. Always verify that corresponding files exist before flagging URLs as broken.
🔇 Additional comments (2)
studiocms (1)
1-1: Confirm submodule commit availability & sync with beta .20 docsThe pointer now targets
029a22ddc227211ac71c7bda565b31b30c90a361.
Please verify that:• The commit exists on the upstream
studiocmsrepo (not a local/ephemeral branch).
• A freshgit clone --recursivecorrectly fetches this commit.
• The commit indeed contains the beta-20 assets referenced in the newly-added guide.Once validated, no further action is needed.
src/content/docs/en/guides/upgrade/version-guides/0-1-0-beta-20.mdx (1)
13-18: Verify QuickUpdate component availability
<QuickUpdate />is imported but not present in other upgrade guides. Ensure the component exists at~/components/QuickUpdate.astro; otherwise the build will fail.If it’s missing, either create the component or replace it with ordinary markdown.
3 participants
Description
Add guide for new beta.20 version
Summary by CodeRabbit
New Features
Chores