Alias v7-dev for latest backpack/crud version does not work yet

[jnoordsij]

The current (preliminary) upgrade guide for v7.x suggests to use v7-dev as version to upgrade to v7 (alpha), however this does not seem to work on my end. I think this is due to the v7 branch not existing, given that seems to be the branch pattern composer expects.

While one solution would be to already create a v7 branch, possibly a neater way to go would be to use a (composer) branch alias. There already is an outdated alias of master to 4.0-dev:
https://github.com/Laravel-Backpack/CRUD/blob/2d7499ed90b453444d6ab721754c045dcd48de79/composer.json#L70-L72

I think adding a dev-main: 7.x-dev (or 7.0.x) alias would probably be the easiest way forward, to easily support various ranges of constraints to refer to the new version, like just ^7.0 or 7.x-dev.

[backpack-ai-bot]

🚨 Bot is not sure about this answer. Please verify. 🚨

Thank you for your question about Backpack's versioning and upgrade process. Based on the information provided in the knowledge sources, I can offer some insights:

You're correct that the v7 branch does not exist yet for Backpack/CRUD. According to the v7 workflow issue, the Backpack team has recently created a v7 branch in CRUD and a v3 branch in PRO to start working on the next major version. However, this is still in the early stages of development.

Your suggestion to use a branch alias in the composer.json file is a good one. However, the knowledge sources don't provide information about current branch aliases for version 7.

The most recent information we have about version development comes from the v7 workflow issue, which indicates that work on version 7 is just beginning. The team is planning several new features and breaking changes for this version, but it's not yet ready for general use or testing.

Given this information, I would recommend the following:

1. Wait for official announcements from the Backpack team about v7 alpha or beta releases.
2. Keep an eye on the Backpack CRUD GitHub repository for updates to the composer.json file or new branches.
3. If you need to use the latest development version, you might consider using the main branch directly, though this is not recommended for production use.

For the most up-to-date and accurate information about upgrading to v7 or using development versions, I recommend reaching out to the Backpack team directly through their official channels or GitHub issues.

ℹ️ Please note our AI Bot does not reply to follow-ups, this will be the only AI answer in this thread. If the AI helped you find the answer, please mark it as answered or write details below so it can learn. Then close the conversation. If not, please give more information for when a human reads this. ℹ️

Relevant sources:

Github Issue (closed): Cant install Backpack 4.0 on Laravel 6.0
Add support for Laravel 8
|Versioning
Github Issue (closed): Updating Laravel 9->10 and error states that backpack CRUD is not supported by L10
Github Issue (closed): [Bug] Method Backpack\CRUD\app\Library\CrudPanel\CrudPanel::addViewNamespaceFor does not exist.
tried to convert a simple prj from v6.x-dev to 6.0
Github Issue (closed): [Bug] Class "Backpack\CRUD\ViewNamespaces" not found in 5.3.6
Github Issue (closed): [Bug] Add MenuCRUD version bump to v5 upgrade docs?
Github Issue (closed): Composer is not updating backpack/crud
use main branch for release-drafter
Github Issue (closed): dev-upgrade issues?
Features
Github Issue (open): v7 workflow
Github Issue (closed): Unable to update in 4.1 composer.json conflict