| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Separately tracking unreleased entries is a good idea, though perhaps confusing for OSS contributors. Let's figure out how to make that work and minimise conflicts.
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for catching. I'd noticed the same happening in the 2.3.5 release as well (a change from 2.3.5 was added to 2.3.3 as a result of a merge conflict resolution), but caught it in time during the release.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
One of the changelog entries for 2.3.6 ended up incorrectly being associated with 2.3.4 due to a bad merge conflict resolution. As a long term fix, we could store unreleased changelog entries in a separate directory and only edit CHANGELOG.md with automation.
Merge / deployment checklist