Conversation
There was a problem hiding this comment.
Pull request overview
Updates the CakePHP installation documentation to use VitePress-native formatting and modernized setup guidance.
Changes:
- Adds page frontmatter and restructures the guide for improved scannability.
- Replaces legacy blockquotes with VitePress callouts and introduces code groups for platform/tool variants.
- Refreshes deployment/web server guidance (including a new Caddy example) and removes outdated references.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
docs/en/installation.md
Outdated
| ::: tip Stay Updated | ||
| Your `composer.json` version constraint controls updates: | ||
| - `"cakephp/cakephp": "5.0.*"` - Patch releases only | ||
| - `"cakephp/cakephp": "^5.0"` - Minor + patch releases (recommended) |
There was a problem hiding this comment.
I wouldn't recommend auto bumping to minor. It should be a more conscious decision. While API maintains BC sometimes config/bootstrap tweaks are required to the app when bumping up a minor.
That is why our skeleton also has patch release level constraint.
There was a problem hiding this comment.
so how do you propose we document this ?
Just like this: ?
- `"cakephp/cakephp": "5.0.*"` - Patch releases only (recommended)
- `"cakephp/cakephp": "^5.0"` - Minor + patch releases (may require config changes)
There was a problem hiding this comment.
if we don't recommend it, why do we have it in our app template then? 😁
There was a problem hiding this comment.
As of 5.2 it was patch releases only https://github.com/cakephp/app/blob/5.2.0/composer.json#L9. I don't know why it was changed for 5.3.
There was a problem hiding this comment.
now we are consistent 👍🏻
@josbeir please adjust it to like you said above (recommended patch releases)
Updates installation.md with VitePress features and removes dated content:
Changes:
::: tip,::: warning,::: danger,::: info)The guide is now more maintainable, easier to navigate, and better aligned with modern development workflows.