Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Composer: Version constraints such as ^1.0@beta are not supported #6050

Closed
hussainweb opened this issue Apr 24, 2020 · 2 comments · Fixed by #6057
Closed

Composer: Version constraints such as ^1.0@beta are not supported #6050

hussainweb opened this issue Apr 24, 2020 · 2 comments · Fixed by #6057
Labels
manager:composer Composer (PHP) package manager priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)

Comments

@hussainweb
Copy link
Contributor

What Renovate type are you using?

I'm self-hosting on GitLab inside a CI pipeline

Describe the bug

Composer supports version constraints such as ^1.0^RC or ^2.0@beta. These values are not supported by Renovate.

Did you see anything helpful in debug logs?

I see these messages in debug log:

 DEBUG: Dependency drupal/daterange_compact has unsupported value 1.x-dev (repository=axl-ks/ks)
DEBUG: Dependency drupal/field_permissions has unsupported value ^1.0@RC (repository=axl-ks/ks)

To Reproduce

In a repo, add any composer.json setup with version constraints such as the above.

Additional context

I think this is the case of just missing support of these style of version constraints available to composer.
@rarkins rarkins changed the title Version constraints such as ^1.0@beta are not supported Composer: Version constraints such as ^1.0@beta are not supported Apr 24, 2020
@rarkins rarkins added manager:composer Composer (PHP) package manager ready type:feature Feature (new functionality) priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others labels Apr 24, 2020
@hussainweb
Copy link
Contributor Author

Thanks for tagging this issue.

An update: After checking on a different project, it seems that the version constraint such as v1.0.0-beta5 works (at least in pinning mode). Whereas, something like v1.0.0@RC doesn't even get replaced in the pinning MR.

If there is any other information I can provide to help, please let me know.

@hussainweb hussainweb mentioned this issue Apr 25, 2020
Merged
rarkins pushed a commit that referenced this issue May 1, 2020
@hussainweb
feat(composer): support stability modifiers (#6050) (#6057)
8f66b5e
@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 19.226.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
manager:composer Composer (PHP) package manager priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(composer): support stability modifiers (#6050)
3 participants
@hussainweb @rarkins @renovate-release