Tom Keller

Hi @niklas302 (and others) - are you sure this is coming from this action and not something else in your workflow? I took a quick look at the dist index.js...

You can compare what we're publishing with what's in GitHub's source here in [core/src/core.ts:192 ](https://github.com/actions/toolkit/blame/main/packages/core/src/core.ts#L191). Specifically, there's a new check for the GITHUB_OUTPUT environment variable that wasn't present in previous...

Hi everyone. Our aim with versioning is to strictly ensure that no breakage will happen within a major version for our software - this is true in this action and...

> @kellertk Do you know what the state is for other popular tasks like: [ECS-Render-Task-Definition](https://github.com/aws-actions/amazon-ecs-render-task-definition/releases)? > > Will there be similar branches available? I'm not sure about that action, because...

Hi everyone, I'll be locking this thread for now (see the comment from @sterlingwes above for why). If you have any issues with the @v1-node16 branch please open a new...

Thank you for posting your feedback here, and our apologies that we’ve been thinking this over for a long time without much forward motion. There are similar requests to implement...

Thank you for posting your feedback here, and our apologies that we’ve been thinking this over for a long time without much forward motion. There are similar requests to implement...

> For better or worse, AWS take feature requests filed through tech support tickets most seriously. That's not necessarily true: when you file a request with the Technical Support button...

LGTM @peterwoodworth, ready to ship?

Hello everybody. Some internal AWS information was posted to this issue; I have removed this information for now. The [comments from](https://github.com/aws/aws-sdk-js/issues/3983#issuecomment-1617270477) @LYTzeng are correct and you should follow this guidance...