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.

@octokitbot octokitbot added the Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR label Apr 9, 2024
@nickfloyd nickfloyd changed the title 🚧 GitHub OpenAPI specifications changed feat: Updates @octokit/types to v13.4.0 Apr 11, 2024
@nickfloyd nickfloyd merged commit 02d6110 into main Apr 11, 2024
@nickfloyd nickfloyd deleted the openapi-update branch April 11, 2024 15:44
@github-actions
Copy link
Contributor

🎉 This PR is included in version 11.1.0 🎉

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 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