Problem/Motivation

The Drupal 11 compatibility patch in the parent ticket was applied incorrectly, causing this error.
9^ needs to be changed to ^9.

CommentFileSizeAuthor
#9 core-update-handle-bad-version-constraint.patch1.45 KBrob230

Issue fork comments_ban-3439305

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

mortona2k created an issue. See original summary.

mortona2k changed the visibility of the branch 3429299-automated-drupal-11 to hidden.

mortona2k opened merge request !4

abhishek_gupta1’s picture

abhishek_gupta1 commented
Assigned: Unassigned » abhishek_gupta1
abhishek_gupta1’s picture

abhishek_gupta1 commented
Assigned: abhishek_gupta1 » Unassigned
Status: Active » Reviewed & tested by the community

I have verified the changes, issue has fixed moving to RTBC++

madhukar k’s picture

madhukar k commented
jeroen_vreuls’s picture

jeroen_vreuls commented
Priority: Normal » Major

This now causes sites with the Update Manager module enabled to fail with the error:

UnexpectedValueException: Could not parse version constraint 9^: Invalid version string "9^" in Composer\Semver\VersionParser->parseConstraint()

It would be really helpful to have a fixed release soon.

olekstkach’s picture

olekstkach commented
Priority: Major » Critical

+1 to the comment above. @rigoucr could this be merged asap please?

rob230’s picture

rob230 commented
StatusFileSize
new core-update-handle-bad-version-constraint.patch1.45 KB

Considering this breaks the core update page it's pretty serious.

Until there can be a new release, I have made a temporary patch (for Drupal core) to handle the situation.

rigoucr made their first commit to this issue’s fork.

  • rigoucr committed 12132978 on 1.0.x authored by mortona2k 
    Issue #3439305 by mortona2k, Rob230, abhishek_gupta1, Madhukar K,...
rigoucr’s picture

rigoucr
Primary language Spanish
commented
Assigned: Unassigned » rigoucr
Status: Reviewed & tested by the community » Fixed

Thank you everyone, and sorry for that typo :/

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.