Skip to content

The BREAKING_CHANGES.md doesn't seem to be getting updated #2230

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.

Sign up for GitHub

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

Jump to bottom
Closed
warlock2k opened this issue Apr 9, 2020 · 3 comments · Fixed by #2351
Closed

The BREAKING_CHANGES.md doesn't seem to be getting updated #2230

warlock2k opened this issue Apr 9, 2020 · 3 comments · Fixed by #2351
Labels
documentation
Milestone
5.5.0

Comments

@warlock2k
Copy link

Are there any breaking changes from 4.0.0 to 5.2.4?
@stale
Copy link

stale bot commented Jul 9, 2020

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 9, 2020
@asbjornu
Copy link
Member

asbjornu commented Jul 9, 2020

Sorry, but this seems to have been forgotten. Thanks for pointing it out!

Yes, there are breaking changes between 4 and 5, otherwise we wouldn't have incremented the major version. Meanwhile BREAKING_CHANGES.md is out of date, taking a scroll through the 5.0.0 Milestone might give you some ideas. #1541 seems to be the most important breaking change going into version 5.

@stale stale bot removed the stale label Jul 9, 2020
@asbjornu asbjornu mentioned this issue Jul 9, 2020
Merged
5 tasks
@arturcic arturcic added this to the 5.5.0 milestone Jul 9, 2020
@arturcic
Copy link
Member

🎉 This issue has been resolved in version 5.5.0 🎉
The release is available on:

Your GitReleaseManager bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation
Projects
None yet
Milestone
5.5.0
Development

Successfully merging a pull request may close this issue.

Update breaking changes asbjornu/GitVersion
3 participants
@asbjornu @arturcic @warlock2k