chore: pin @aws/agentcore-cdk version and auto-sync on release#811
Merged
chore: pin @aws/agentcore-cdk version and auto-sync on release#811
Conversation
Pin the @aws/agentcore-cdk dependency in the vended CDK project template to an exact version (0.1.0-alpha.17) instead of using a caret range. This eliminates the release-ordering race condition where the CLI release references a CDK version that hasn't been published to npm yet. Also adds an auto-sync step to the release workflow that fetches the latest @aws/agentcore-cdk version from npm during release preparation, so the pinned version is always up-to-date in each CLI release PR.
Contributor
Package TarballHow to installnpm install https://github.com/aws/agentcore-cli/releases/download/pr-811-tarball/aws-agentcore-0.8.0.tgz |
Contributor
Coverage Report
|
aidandaly24
approved these changes
Apr 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@aws/agentcore-cdkin the vended CDK template (src/assets/cdk/package.json) to an exact version (0.1.0-alpha.17) instead of a caret range (^0.1.0-alpha.1)@aws/agentcore-cdkfrom npm during release prep, so each CLI release PR automatically includes the latest CDK versionWhy
The caret range (
^) creates a release-ordering race condition: if the CLI is released before the CDK constructs package is published to npm, users runningagentcore createwould get a stale or missing CDK version. Pinning eliminates this entirely.How it works
During
prepare-releasein the release workflow (before the version bump), a new step:npm view @aws/agentcore-cdk versionto get the latest published versionsrc/assets/cdk/package.jsonRelease flow after this change
Test plan