-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
docs: wiki and changelog updates for v6.1.0 release #416
Conversation
thanks for the heads up re: deprecating v4 migration code. Anecdotally, there's still plenty of folks unaware of this successor project, i.e. still using the last version from Jules-WinnfieldX's repo. So, once they discover v. 6.x (or 7.x?) it means they're SoL. I'm not saying you should not remove the v4 migration code, but maybe provide some guidance for such people. E.g., forcibly install some known good old version first, do |
Added a disclaimer in the v4 import section of the documentation. It will be updated to be more specific when support is eventually dropped. |
Co-authored-by: Jacob <[email protected]>
Move to the next release
* docs: update changelog * docs: add ruff badge * chore: bump version to v6.1.0 * docs: add ruff hyperlink * docs: fix README padding * docs: update CLI overview (wiki) * docs: add v4 deprecation disclaimer * docs: update 6.0.0 hyperlink * docs: update changelog * docs: fix typo * docs: update v4 import disclaimer Co-authored-by: Jacob <[email protected]> * docs: remove db fix from changelog Move to the next release --------- Co-authored-by: Jacob <[email protected]>
Assumes hash-db-error-fix #407 will be merged before releasePostponed for the next release