Skip to content

Conversation

@octokitbot
Copy link
Contributor

If there are any new endpoints, then the code changes will likely required an update of @octokit/types. It should have received a pull request as well, merge & release it first. The @octokit/types should be updated automatically shortly after in this pull request.

Make sure to update the commits so that the merge results in helpful release notes, see Merging the Pull Request & releasing a new version.

In general

  • Avoid breaking changes at all costs
  • If there are no typescript or code changes, use a docs prefix
  • If there are typescript changes but no code changes, use fix(typescript) prefix
  • If there are code changes, use fix if a problem was resolved, feat if new endpoints / parameters were added, and feat(deprecation) if a method was deprecated.

wolfy1339 and others added 2 commits June 10, 2023 09:21
The changes were already made in the generated output. This doesn't make any further changes
@octokitbot octokitbot added the Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR label Jun 10, 2023
@wolfy1339 wolfy1339 changed the title 🚧 GitHub OpenAPI specifications changed fix: bump version of @octokit/types Jun 10, 2023
@wolfy1339 wolfy1339 merged commit 4308c1c into main Jun 10, 2023
@wolfy1339 wolfy1339 deleted the openapi-update branch June 10, 2023 21:23
@github-actions
Copy link
Contributor

🎉 This PR is included in version 7.2.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link
Contributor

🎉 This PR is included in version 8.0.0-beta.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

released on @beta released Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants