Skip to content

NG UPDATE NOT WORKING going from angular 17 to angular 18 #28030

@harpreetsinghravi

Description

@harpreetsinghravi

Command

update

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

I have been migrating my projects from angular 17 to angular 18 using the update guide this week. Ever since v18.1.0 was released, the ng update command started to fail. 2 of my projects migrated just fine to version 18.0.6.

The reason for the failure is because of the temporary cli version 18.1.0 that is installed. The error messages is - "No matching version found for @angular-devkit/architect@0.1801.0."

Seems like this package is missing. Can this be addressed as I can no longer migrate any project to version 18 ? Is there a way to specify which temporary cli version to use? If yes, then I can use this as a workaround for now. Please advise.

Minimal Reproduction

I have been migrating my projects from angular 17 to angular 18 using the update guide this week. Ever since v18.1.0 was released, the ng update command started to fail. 2 of my projects migrated just fine to version 18.0.6.

The reason for the failure is because of the temporary cli version 18.1.0 that is installed. The error messages is - "No matching version found for @angular-devkit/architect@0.1801.0."

Seems like this package is missing. Can this be addressed as I can no longer migrate any project to version 18 ? Is there a way to specify which temporary cli version to use? If yes, then I can use this as a workaround for now. Please advise.

Exception or Error

No response

Your Environment

angular v 17.3.11

Anything else relevant?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions