Amir Sekhavati

We just started using this Action today and hit a similar issue. I believe its due to [this caveat](https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#triggering-a-workflow-from-a-workflow) noted in the GitHub Action docs and the fact that this...

@moollaza I haven't got an immediate use for it myself. I suggested it as an option to address [Spice#2113](https://github.com/duckduckgo/zeroclickinfo-spice/issues/2113).

I'm also having similar issues to folks above. In our case we were guarding against multiple deploys to AWS happening concurrently but the action doesn't seem to be working as...

> Hope this makes more sense to you now! This will be patched soon so you won't have to worry about this work around @Spence-S thank you for sharing the...

Same issue is reproducible with the following basic Lambda using TypeScript 5.3.3: ```typescript import { type Handler } from "aws-lambda"; import middy from "@middy/core"; const baseHandler: Handler = async (event)...

I'm also hitting this when using SNS as an event destination, any workaround or movement on this issue?

So thought I’d share the workaround I’ve put in place as it may help someone else who comes across this thread. In my situation I was configuring a basic fan-out...

I'm still seeing this issue in `3.34.0`. Interestingly there are no type errors if my package _only_ contains `@aws-sdk/util-dynamodb`. But as soon as I install `@aws-sdk/client-dynamodb` the aforementioned TypeScript errors...