fix(typescript): add enum to delete#ref_type to match create event (via [@octokit/webhooks-definitions v3.58.1](https://github.com/octokit/webhooks/releases/tag/v3.58.1))

[octokitbot]

A new release of @octokit/webhooks was just released 👋🤖

This pull request updates the TypeScript definitions derived from @octokit/webhooks. I can't tell if the changes are fixes, features or breaking, you'll have to figure that out on yourself and adapt the commit messages accordingly to trigger the right release, see our commit message conventions.

[wolfy1339]

@gr2m I had to re-run the workflow, when it ran initially it didn't pick up the latest version.

[wolfy1339]

And the same thing happened again... What is going on with npm? It doesn't pick up the latest release version

[G-Rath]

@wolfy1339 npm is backed by a sizable cache setup, so it can sometimes take upwards of 10 minutes before a new package propagates to the whole of the registry

[wolfy1339]

That's understandable, however why has the issue never come up before until now

[G-Rath]

I've definitely had this issue a few times over at my repo - it seems to me like it happens typically when you do a couple of releases very quickly.

---

However, looking at the logs & PR, it seems to me that it has picked up the latest version? What version would you expect it to be bumping us to in this PR?

[wolfy1339]

Everything is fine now. But I had to manually re-request the action be run.

[G-Rath]

Oh, I didn't think you had because it said "Update #100: Repository dispatch triggered by octokit-release-notifier bot" but all good.

In that case, that'd point to the app being the problem rather than npm, since its the one that should be triggering the actions.
I suspect it might be some sort of debounce somewhere that occurs when you have a few releases happen very quickly.

[wolfy1339]

Can we check if the release is a pre-release and then install using the release's version number instead of relying on npm to update @latest (and the caching involved)?

[G-Rath]

That caching is inherent in the whole system, it's not just the @latest tag.

But the fact that the action didn't fire at all means that we should be looking at the app rather than the action :)

[gr2m]

I've built https://github.com/gr2m/await-npm-package-version-action/ to address the delay between an npm publish and the availablity of the new version in the registry, e.g. see

https://github.com/octokit/openapi-types.ts/blob/ef4ea6bdb24d85cb094bba8751829bbecc835ffd/.github/workflows/update.yml#L34-L37

Let's add that to this repository's update workflow

[gr2m]

when merging, ideally we would make the squash commit more useful than

feat: update types from @octokit/webhooks-definitions

depending on what changes are relevant to @octokit/webhooks users. In this case something like this maybe?

fix(typescript): add enum to delete#ref_type to match create event (via @octokit/webhooks-definitions v3.58.1)

[github-actions]

🎉 This PR is included in version 7.24.3 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 8.0.2 🎉

The release is available on:

• GitHub release
• npm package (@next dist-tag)

Your semantic-release bot 📦🚀