Skip to content

Conversation

octokitbot
Copy link
Contributor

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 Tests, Refactorings, Automation, etc label Mar 18, 2025
@wolfy1339 wolfy1339 changed the title 🚧 GitHub OpenAPI specifications changed feat: new /orgs/{org}/issue-types, /orgs/{org}/issue-types/{issue_type_id} enpoints Mar 18, 2025
@wolfy1339 wolfy1339 merged commit b879eb9 into main Mar 18, 2025
8 checks passed
@wolfy1339 wolfy1339 deleted the openapi-update branch March 18, 2025 23:40
Copy link
Contributor

🎉 This PR is included in version 9.6.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 Tests, Refactorings, Automation, etc
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants