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.

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

cdk-assets: Cannot install cdk-assets@latest in CodePipeline #33491

Closed
1 task
alexanderlazarev0 opened this issue Feb 18, 2025 · 12 comments
Closed
1 task

cdk-assets: Cannot install cdk-assets@latest in CodePipeline #33491

alexanderlazarev0 opened this issue Feb 18, 2025 · 12 comments
Assignees
Labels
@aws-cdk/aws-codepipeline Related to AWS CodePipeline bug This issue is a bug. effort/medium Medium work item – several days of effort p1

Comments

@alexanderlazarev0
Copy link

Describe the bug

Currently have the following issue on all assests (File & Docker) in Codepipeline:

Entering phase INSTALL
[Container] 2025/02/18 16:22:31.177078 Running command npm install -g cdk-assets@latest
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @aws-sdk/lib-storage@3.750.0
npm warn Found: @aws-sdk/client-s3@3.741.0
npm warn node_modules/cdk-assets/node_modules/@aws-sdk/client-s3
npm warn   @aws-sdk/client-s3@"3.741" from cdk-assets@3.0.0-rc.144
npm warn   node_modules/cdk-assets
npm warn     cdk-assets@"3.0.0-rc.144" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer @aws-sdk/client-s3@"^3.750.0" from @aws-sdk/lib-storage@3.750.0
npm warn node_modules/cdk-assets/node_modules/@aws-sdk/lib-storage
npm warn   @aws-sdk/lib-storage@"^3.750.0" from cdk-assets@3.0.0-rc.144
npm warn   node_modules/cdk-assets
npm warn
npm warn Conflicting peer dependency: @aws-sdk/client-s3@3.750.0
npm warn node_modules/@aws-sdk/client-s3
npm warn   peer @aws-sdk/client-s3@"^3.750.0" from @aws-sdk/lib-storage@3.750.0
npm warn   node_modules/cdk-assets/node_modules/@aws-sdk/lib-storage
npm warn     @aws-sdk/lib-storage@"^3.750.0" from cdk-assets@3.0.0-rc.144
npm warn     node_modules/cdk-assets
npm error code ETARGET
npm error notarget No matching version found for @aws-cdk/cloud-assembly-schema@^40.1.0.
npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.

I can understand why this is an issue with cdk-assets@3.0.0-rc.144, but why does CodePipeline try to install latest version.

Apologies if this is not a cdk issue.

Regression Issue

  • Select this option if this issue appears to be a regression.

Last Known Working CDK Version

cdk-assets@3.0.0-rc.143

Expected Behavior

No installation errors.

Current Behavior

Installation errors.

Reproduction Steps

My pipeline:

const pipeline = new CodePipeline(this, 'pipeline', {
            pipelineName: props.pipelineName,
            synth: new ShellStep('synth', {
                input: CodePipelineSource.codeCommit(
                    props.fromCodeCommitRepository,
                    props.fromCodeCommitBranch
                ),
                commands: ['npm ci', 'npm run build', 'npx cdk synth'],
            }),
        })

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

/

Framework Version

No response

Node.js Version

/

OS

/

Language

TypeScript

Language Version

No response

Other information

No response

@alexanderlazarev0 alexanderlazarev0 added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Feb 18, 2025
@github-actions github-actions bot added the @aws-cdk/aws-codepipeline Related to AWS CodePipeline label Feb 18, 2025
@tomburge
Copy link

I'm getting the same issue. Pipeline worked when it ran right before the new release.

@leantorres73
Copy link

leantorres73 commented Feb 18, 2025

The issue is that latest cdk-assets is pointing to cloud-assembly-schema version 40.1.0 and it does not exist yet (latest version deployed is 40.0.7).

@tomburge
Copy link

The issue is that latest cdk-assets is pointing to cloud-assembly-schema version 40.1.0 and it does not exist yet (latest version deployed is 40.0.7).

Next time they should probably deploy dependencies in the correct order. :)

@leantorres73
Copy link

leantorres73 commented Feb 18, 2025

The curious thing about all this is the github repo cloud-assembly-schema was archived yesterday. 🤔

I bet that's probably why the project didn't get a new release and everything fails.

@tomburge
Copy link

The curious thing about all this is the github repo cloud-assembly-schema was archived yesterday. 🤔

I bet that's probably why the project didn't get a new release and everything fails.

I wonder if that was done by mistake...hard to believe a hard dependency for a release candidate would be archived.

@ardens-jw
Copy link

Just adding some more engagement to this issue - quite critical for a lot of people using CDK pipelines I'd imagine. Lots of sad deployment pipelines right now!

@ashishdhingra ashishdhingra added p1 effort/medium Medium work item – several days of effort and removed needs-triage This issue or PR still needs to be triaged. labels Feb 18, 2025
@ashishdhingra
Copy link
Contributor

Added to appropriate project board and reported offline to the team.

@dcaruso-pathpoint
Copy link

Does anyone have a work a round?

@jeffreymrussell
Copy link

It seems to be fixed already.

@tommy-marginedge
Copy link

https://www.npmjs.com/package/cdk-assets/v/3.0.0-rc.143?activeTab=code they've reverted the change so that cloud-assembly-schema is no longer pointing at an unreleased version.

@rix0rrr
Copy link
Contributor

rix0rrr commented Feb 18, 2025

We pulled the affected versions and corrected the release tag. Thanks for reporting everyone!

@rix0rrr rix0rrr closed this as completed Feb 18, 2025
Copy link

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 18, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
@aws-cdk/aws-codepipeline Related to AWS CodePipeline bug This issue is a bug. effort/medium Medium work item – several days of effort p1
Projects
None yet
Development

No branches or pull requests

9 participants