-
Notifications
You must be signed in to change notification settings - Fork 360
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
Prepare release of 1.11.0 #49
Conversation
Kinda early for a release. Shouldn't we fix more of the issues detected by the static analyzers first? |
It is never too early =) It has been almost a month, there has been no issues reported. We will not run out of version numbers =) |
9ac4d3a
to
76f4d3d
Compare
I agree it would be good to push a new version even though it is mostly styling and such. Will keep it clean for future versions as well |
Shouldn't this PR be deleting those entries from the BC config? |
Hmm, I guess we want a green build for the tag though. |
Correct. We can update the BC config file after the minor release. |
We should release this after #53 |
I agree to push this but maybe extend the changelog a little on stuff that actually changed as well? Like splitting the docs, psr12 compliance etc |
In my mind, only code related changes should be in the change log. I'll add a note about the code style |
The diff from 1.10.1 to main is quite large because of the CS changes.
I suggest a new release so future diffs are easier to read. Current main also have some features in it.
See diff without code style changes: v1.10.1...16f051e