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-nodejs-function-from-entry@0.3.0

Minor Changes

• #1753 24c8dc1 Thanks @toddhainsworth! - Allow overriding the resolved Lambda handler, needed for handler-wrapping mechanisms (e.g. a Lambda Layer wrapper) that require a fixed handler string. Existing callers are unaffected — omitting handler still defaults to the resolved index.handler.

@aligent/cdk-aspects@0.8.1

Patch Changes

• #1752 2ec5779 Thanks @toddhainsworth! - Skip CDK-managed singleton/framework resources in LambdaAndStepFunctionVersioningAspect so it no longer adds aliases/versions to handlers like the BucketDeployment custom resource.

[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.