-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BREAKING CHANGE: deprecate GHES 3.2 #286
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocked by #285
344003d
to
e97d9d0
Compare
@wolfy1339 since this is a breaking change with the deprecation of GHES 3.2 and the PR description says to "avoid breaking changes at all costs", what's the correct path forward here? |
In cases like these where support is removed for a GHES version, a major version bump is unavoidable. |
BREAKING CHANGE should be in the commit body commit message, like so:
that way we can have a better idea of the changes in the changelog and commit history |
🎉 This PR is included in version 15.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
build: cache
as commit messagefix: ...
feat: ...
BREAKING CHANGE: ...
to the commit body (not subject!) to trigger a breaking change.