chore: release packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@aligent/cdk-secure-rest-api@1.2.0

Minor Changes

• #1720 2649bf8 Thanks @toddhainsworth! - Support nested (multi-segment) route paths in the routes helper. Paths such as rewards/accounts/{accountId}/redeem now create the intermediate resources instead of throwing ResourceSPathPartOnly at synth time. Routes sharing a common prefix resolve idempotently.

  Add a deployOptions prop (CDK StageOptions) so the deployed stage name and other stage settings can be configured. Defaults to the CDK prod stage when omitted.

@aligent/cdk-aspects@0.6.5

Patch Changes

• #1717 3dd2e7a Thanks @kai-nguyen-aligent! - Fix conflicting throughput config when aspect overrides DynamoDB billing mode

@aligent/cdk-header-change-detection@1.7.11

Patch Changes

• #1715 19fb43f Thanks @aikido-autofix! - [Aikido] Fix security issue in axios via minor version upgrade from 1.16.1 to 1.18.0

@aligent/cdk-prerender-proxy@2.5.10

Patch Changes

• #1715 19fb43f Thanks @aikido-autofix! - [Aikido] Fix security issue in axios via minor version upgrade from 1.16.1 to 1.18.0

[github-actions]

⚠️ No Changeset Detected

This pull request modifies code that affects the following packages (detected by Nx):

Affected Packages:

• @aligent/cdk-cdk-aspects
• @aligent/cdk-constructs

If this PR should trigger a release:

yarn changeset

Follow the prompts to select the affected packages and describe your changes.

If this PR should NOT trigger a release:

• Documentation-only changes
• Internal refactoring with no API changes
• Test updates
• Build/CI configuration changes
• Changes only to root files (package.json, workflows, etc.)

In this case, no action is needed - this comment is just a reminder for reviewers.

This check uses Nx to accurately detect which packages are affected by your changes. If you're unsure whether a changeset is needed, please ask a maintainer!

🔧 Commands & Tips

# Add a changeset for your changes
yarn changeset

# Check which packages Nx thinks are affected
npx nx show projects --affected

# Check current changeset status
yarn changeset:status

# Add an empty changeset if no release needed
yarn changeset --empty

Pro tip: When running yarn changeset, select only the packages listed above that you actually changed the public API of.