[BUG][Functional] Upgrade to 1.6.3 from 1.6.2 is failing on ASEA-InstallerPipeline Step

[muhammadumeruzair]

The Upgrade to 1.6.3 from 1.6.2 is failing on ASEA-InstallerPipeline Step and producing below error,

added 1 package in 10s

1 package is looking for funding
run npm fund for details

[Container] 2025/04/30 09:10:49.508023 Running command pnpm install --frozen-lockfile
Scope: all 137 workspace projects
·WARN· There are cyclic workspace dependencies: /codebuild/output/src3464907631/src/src/lib/common, /codebuild/output/src3464907631/src/src/lib/common-config_
·_WARN· Ignoring not compatible lockfile at /codebuild/output/src3464907631/src/pnpm-lock.yaml
·ERR_PNPM_NO_LOCKFILE· Cannot install with "frozen-lockfile" because pnpm-lock.yaml is absent

Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile"_

_[Container] 2025/04/30 09:10:50.689598 Command did not exit successfully pnpm install --frozen-lockfile exit status 1
[Container] 2025/04/30 09:10:50.730448 Phase complete: INSTALL State: FAILED
[Container] 2025/04/30 09:10:50.730466 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: pnpm install --frozen-lockfile. Reason: exit status 1

Steps To Reproduce

1. Go to pipelines and edit the ASEA-InstallerPipeline
2. Upgrade the GitHub reference to latest version of as below,
   Repository | aws-samples/aws-secure-environment-accelerator
   and release/v1.6.3
3. After connecting to latest version save the GitHub source edit
4. Release the pipeline changes
5. After Source, Validate Parameter the next step is Deploy where this fails and produces above error.
6. The downgrade back to v1.6.2 was worked successfully.