-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: use new types from @octokit/webhooks-definitions
#406
Conversation
2fc7296
to
4de05e7
Compare
c734c33
to
66ea236
Compare
66ea236
to
3b05915
Compare
I think we're good to go - note this'll be rebased at least twice when I merge in #403 & #410, so approves won't stick until then While I've marked everything in the old generated payloads as |
3b05915
to
7ce9c52
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't feel confident enough to give an approval but, for what I read, everything looks good to me :)
ef605e6
to
e9a4e48
Compare
e9a4e48
to
695066b
Compare
Should these deprecations be part of this PR or did they already happen?
|
4cd9246
to
ec4b1e7
Compare
I've pinned the version constraint for The reason for this is that otherwise it can be updated by anything that regenerates the lockfile, which we've got renovate doing every week, but we need to make sure |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My understanding is that we can merge this in as a feature release, as it does not introduce any breaking changes? If so, +1 for merging from me. Otherwise please let me know what the breaking changes are. If breaking changes are TypeScript types only we can release a feature release, I don't consider TypeScript type changes breaking changes as they don't affect production code, they only occur at build time
6bbf256
to
ea27ffa
Compare
932bb28
to
9481899
Compare
Alright, let's do this! we can fix up any issues in post 😎 |
well, that's odd. I'll see if I can figure out what's going wrong. |
I know why this is breaking - will have a PR up shortly |
🎉 This PR is included in version 7.22.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Here it is 🎉
There's a few things to polish off and discuss before landing this, but the bulk of it is done so making the PR now.
I'm breaking some things out into their own little PRs where possible.