Merlin Gough

> I am currently having this issue when I upgrade the version of my NestJS packages to v8, I was trying to implement versioning so I have to upgrade to...

I'm a little late to the party, but I'd like to join the slack if possible. I can't guarantee any significant contributions at this time, but I'd like to get...

Hi @coltenkrauter , I'm not sure if it's any help, I was just browsing and spotted your issue, but I have done something similar. It's similar to the approach you've...

This looks like an issue that several people have reported on the email-templates module (https://github.com/forwardemail/email-templates/issues/435) potentially relating to how the files have been bundled. Strangely people with various setups seem...

> I figured out it is a 403 error btw, and the bucket name is not taken Hi @Alien10123 - Delayed response, and I'm not a contributor just a user...

I've been digging around in this repo to try and work out the current state of things. It looks like last year there was a PR opened to remove the...

We're also seeing this issue. We have two actions, both running Node16. The only difference in the one which is breaking the deploy CLI tool is that it has `dependencies`...

I've realised this is actually linked to the fact that we have an action which we set `deployed: False` for specific environments/tenants. The deploy-cli tries to set the triggers: ```...

I have now discovered that once something is set to `deployed: True` it can't be set to false again. For me this issue is definitely tied to the lack of...

> This seems to be a separate issue, no? I'm not even sure if you can undeploy an action, that's something we'll also need to investigate. Nonetheless, I'd like to...