What's Changed
- feat: CFN auto-generated names follow AWS {stack}-{logicalId}-{SUFFIX… by @Nahuel990 in https://github.com/Nahuel990/ministack/pull/57
[1.1.15] — 2026-04-01
Added
- Lambda Node.js runtime —
nodejs14.xthroughnodejs22.x(and any futurenodejsN.x) now fully execute via local subprocess (node) or Docker; supportsCreateFunction,UpdateFunctionCode,Invokeincluding async handlers; layers resolved tonodejs/node_modules;nodejs24.xauto-maps via pattern
Fixed
- CloudFormation auto-generated physical names — resources without explicit names now follow the AWS pattern
{stackName}-{logicalId}-{SUFFIX}with a 13-char uppercase alphanumeric suffix; service-specific rules applied (S3: lowercase, max 63; SQS: max 80; DynamoDB: max 255; Lambda/IAM/EventBridge: max 64). Fixes CDK stacks that omit explicit resource names producing untraceablecfn-xxxnames - Import cleanup — moved lazy stdlib imports (
base64,fnmatch,re,datetime,urllib) to module level acrosssqs,cloudwatch_logs,glue,cognito,rds,apigateway,apigateway_v1; removed duplicateos/reimports ins3
Tests
- 3 new Node.js Lambda tests (create+invoke, nodejs22.x, UpdateFunctionCode)
- 4 new CFN physical name tests (S3/SQS/DynamoDB auto-name pattern, explicit name not overridden)
- 815 tests total, all passing