Skip to content

Commit 39151d0

Browse files
authored
chore(cli-integ): make the version of cli-lib-alpha switchable (#33450)
The `@aws-cdk/cli-lib-alpha` package is vended as an alpha package in the old pipeline. That means its version number is `2.178.1-alpha.0` for a real release, or `2.178.1-alpha.999` for a release candidate, with the version component matching the framework version. In the new pipeline, we'll have to decouple from the framework version to the CLI version anyway, and I don't want to have to rebuild this version mangling logic in projen. Instead, we'll just always take the CLI version and append `-alpha.0`. That may mean we'll end up with a release candidate version of `-rc.0-alpha.0`, which looks weird but I don't think will break anything. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
1 parent 523e0f0 commit 39151d0

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

packages/@aws-cdk-testing/cli-integ/lib/with-cli-lib.ts

+8-1
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,16 @@ export function withCliLibIntegrationCdkApp<A extends TestContext & AwsContext &
3737
}
3838

3939
const alphaInstallationVersion = fixture.packages.requestedAlphaVersion();
40+
41+
// cli-lib-alpha has a magic alpha version in the old release pipeline,
42+
// but will just mirror the CLI version in the new pipeline.
43+
const cliLibVersion = process.env.CLI_LIB_VERSION_MIRRORS_CLI
44+
? `${fixture.packages.requestedCliVersion()}-alpha.0`
45+
: alphaInstallationVersion;
46+
4047
await installNpmPackages(fixture, {
4148
'aws-cdk-lib': installationVersion,
42-
'@aws-cdk/cli-lib-alpha': alphaInstallationVersion,
49+
'@aws-cdk/cli-lib-alpha': cliLibVersion,
4350
'@aws-cdk/aws-lambda-go-alpha': alphaInstallationVersion,
4451
'@aws-cdk/aws-lambda-python-alpha': alphaInstallationVersion,
4552
'constructs': '^10',

0 commit comments

Comments
 (0)