Skip to content

Conversation

@octokitbot
Copy link
Contributor

See what changed at https://github.com/octokit/routes/releases/latest.

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, then update the @octokit/types version in package.json 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.

@gr2m gr2m changed the title 🚧 GitHub REST API Endpoints changed 🎤 I got 99 problems, but a breaking change ain't one Jun 7, 2020
Copy link
Contributor

@gr2m gr2m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BlackLivesMatter

@gr2m gr2m added the Type: Feature New feature or request label Jun 7, 2020
@gr2m gr2m merged commit bf089f4 into master Jun 7, 2020
@gr2m gr2m deleted the routes-update branch June 7, 2020 17:56
@github-actions
Copy link
Contributor

github-actions bot commented Jun 7, 2020

🎉 This PR is included in version 3.17.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

Type: Feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants