Peter Wong

https://github.com/actions/delete-package-versions/issues/74 seems related to this and the real cause of the problem

This issue has caused our organization npm package registry to grow too large (started August/September), accumulating so many non-stable versions, because our retention policy is not being processed, via this...

> it means new npm packages published after August will not appear on GraphQL output. I really want to start a discussion on this. Our organization really needs this GitHub...

As an organization (and paying for GitHub Enterprise), we still a prefer a GitHub-authored/sanctioned action for processing our package retention policies. Some organizations have tight security restrictions on what open-source...

Getting the lambda context via `getCurrentInvoke()` and subsequently calling `context.succeed()` with the event would break the abstraction in the route handler of using _express_ request/response model. An alternative approach is...

> This has been resolved with [v4.0.0](https://github.com/actions/delete-package-versions/releases/tag/v4.0.0) of this Action. > > Required steps to use this Action for the new GitHub Packages architecture: > > * Update action’s version...

With #74 being fixed/closed starting with v4.0.0 or later of the action, this issue can also be closed. Would the OP or others provide a workflow YAML and/or run logs...