When updating from a beta to full release, remove the ^beta composer constraint

[YesCT]

Tell us more.

I'll try and find a recent example to follow-up with to add more details.

[YesCT]

Here is an example of a recent update renovate did:

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
drupal/facets (source) ^3.0.0-beta4@beta -> 3.0.0@beta

Composer Lock Diff
Production Changes From To Compare
drupal/facets 3.0.0-beta4 3.0.0 ...

And here is an example of a manual change we needed to make afterwards:

composer.json:

-        "drupal/facets": "3.0.0@beta",
+        "drupal/facets": "^3.0.0",

[YesCT]

I would still like to find an example of renovate removing ^ when updating a beta. That I think could be an important clue to where to do a fix/change.

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team