feat: BREAKING CHANGES: renames [repository-rule-params-code-scanning-threshold to repository-rule-params-code-scanning-tool, security_alerts to security_alerts_threshold], renames fields[repository-rule-params-code-scanning-threshold.alerts to repository-rule-params-code-scanning-tool.alerts_threshold, repository-rule-params-code-scanning-threshold.security_alerts to repository-rule-params-code-scanning-tool.security_alerts_threshold]

octokit / openapi-types.ts

Generated TypeScript definitions based on GitHub's OpenAPI spec

MIT License

40 stars 10 forks source link

Closed octokitbot closed 6 months ago

octokitbot commented 6 months ago

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 changes, use build: cache as commit message
If there are there are only updates, use fix: ...
If there are any new additions, use feat: ...
If there are breaking changes, keep the previous ones and deprecate them. Only if there is no other way, add BREAKING CHANGE: ... to the commit body (not subject!) to trigger a breaking change.

octokitbot commented 6 months ago

:tada: This PR is included in version 22.0.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket: