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 an Altair 4.2.1 release with back-ported bug fixes and warnings #2844
Comments
I went through all commits in master which are not in |
Thanks for checking @binste. So the branch Only the release date needs to be changed in the release note for version 4.2.1 when known, see here. Following the release notes from step 7 it can be tagged and published as version Afterwards it is probably easier to include a single commit in the https://github.com/altair-viz/altair-viz.github.io repository with the change log changes for |
This plan sounds good to me as well. I went through all the merged PRs since the last release and didn't see anything of significance other than what has been mentioned here already. Maybe we should make a new minor release of altair_saver too to fix that selenium issue? |
This issue is on backporting bug fixes for Altair 4.2.
PR: #2827 is for the fix on jsonschema and replacing
iteritems
withitems
PR: #2843 is about the deprecation of Vega wrappers and VegaLite 3 wrappers
This preparation is done in the
v4.2.X
as base branch.I think this would be sufficient, but if there are still things missing we can add them here.
The text was updated successfully, but these errors were encountered: