November 18, 2026 · v1.5.42
v1.5.42 adds ECR pull-through cache rules that fill on first pull, repository creation templates, their CloudFormation resources and the Lambda nodejs26.x runtime, with fixes to cross-account authorization across SQS, DynamoDB, Secrets Manager, S3, IAM, Lambda and SNS, Step Functions definition validation, RDS input validation and engine versions, CloudFormation stack events and CloudFront KeyValueStore ARNs.
CreatePullThroughCacheRule, UpdatePullThroughCacheRule, DeletePullThroughCacheRule, DescribePullThroughCacheRules, ValidatePullThroughCacheRule and Put/Get/DeleteRegistryPolicy, with AWS's errors. A rule creates the AWSServiceRoleForECRPullThroughCache service-linked role, and validation checks the rule's own secret and role without contacting the upstream. Reported by @kharabasz.GET/HEAD of a tag, or an ECS task asking for an uncached <prefix>/<path>:<tag>, fills the cache from the host daemon's copy or a daemon pull with the host's registry login. Nothing is pushed and the rule's secret is never sent. An image that cannot be had answers 404 MANIFEST_UNKNOWN, and BatchGetImage does not fill the cache, as on AWS. Reported by @kharabasz.CreateRepositoryCreationTemplate, UpdateRepositoryCreationTemplate, DeleteRepositoryCreationTemplate and DescribeRepositoryCreationTemplates. A cache fill creates its repository from the PULL_THROUGH_CACHE template with the longest matching prefix, else ROOT. Reported by @kharabasz.AWS::ECR::PullThroughCacheRule, AWS::ECR::RepositoryCreationTemplate and AWS::ECR::RegistryPolicy. Stacks create, update and delete them through the ECR API, with its errors. Reported by @kharabasz.nodejs26.x. The Docker executor runs nodejs26.x functions on public.ecr.aws/lambda/nodejs:26. Reported by @whittin3.AUTH=true, SQS GetQueueUrl, DynamoDB item calls by table ARN, Secrets Manager reads and writes by secret ARN and S3 bucket policies naming another account's role or user now evaluate the owner's resource policy and the caller's identity policy. DynamoDB and SNS tag and policy actions, IAM paths and Lambda iam:PassRole are authorized against the right resource, and denials name it. SQS SenderId carries the user or role ID. Reported by @TheKerbycz.ValidateStateMachineDefinition reports SCHEMA_VALIDATION_FAILED, MISSING_TRANSITION_TARGET and MISSING_END_STATE, and create and update answer InvalidDefinition without storing the definition. Reported by @kharabasz.CreateDBInstance, ModifyDBInstance, CreateDBCluster, ModifyDBCluster and AddTagsToResource refuse the values AWS refuses, with AWS's messages, and concurrent creates with one identifier leave exactly one. DescribeDBEngineVersions lists the versions AWS offers in us-east-1 with AWS's attributes and defaults. Contributed by @Areson. Reported by @kharabasz.SELECT with an OR or IN on a key reads each key in turn, charged and paged as AWS does, and validation messages follow AWS's order and wording. Reported by @hicksy and the paritysuite.org project.aws:cloudformation: tags, DescribeStackEvents reports ResourceProperties with a NoEcho value as ****, and a table's stream label has no trailing Z. Contributed by @antonie-popovic.Id, as on AWS, and CloudFront's own "The request could not be satisfied" pages have the full body a real distribution sends. Contributed by @antonie-popovic.StartBuild status. StartBuild answers IN_PROGRESS in QUEUED with buildComplete false, as AWS does, instead of a finished build. Contributed by @antonie-popovic.StartSyncExecution and DiscoverInstances, reach MiniStack from in-process Node functions, also under USE_SSL. Contributed by @antonie-popovic.AccessDenied "Request has expired" body carries X-Amz-Expires, Expires and ServerTime, as on AWS.docker pull ministackorg/ministack:1.5.42 docker run -d -p 4566:4566 ministackorg/ministack:1.5.42
Or pin in compose.yaml:
services:
ministack:
image: ministackorg/ministack:1.5.42
ports:
- "4566:4566"
Issues and PRs welcome on GitHub. Discussion on r/ministack.