Skip to content
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

v0.5.0 #615

Merged
merged 1 commit into from
Oct 12, 2020
Merged

v0.5.0 #615

merged 1 commit into from
Oct 12, 2020

Conversation

kjvalencik
Copy link
Member

Publish 0.5.0 as a prerequisite to yanking 0.4.1 and 0.4.2.

RELEASES.md Outdated

_Re-publish_

Versions `0.4.1` and `0.4.2` included a breaking change in `neon-runtime`. At the time, this was considered acceptable because `neon-rutime` is considered an internal crate and not part of the public API. However, it was discovered, after publishing, that `neon-serde`, a commonly used crate in the `neon` ecosystem, contained a direct dependency on `neon-runtime`. In order to best support users, versions `0.4.1` and `0.4.2` were "yanked" and re-published as `0.5.0`.

This comment was marked as resolved.

@jonahpelfrey
Copy link

@kjvalencik I need to update a neon project to be compatible with Node v16. This project also requires neon-serde. Is there currently a solution for this problem? Or are projects with neon-serde required to stay at neon v0.5.0?

@kjvalencik
Copy link
Member Author

@jonahpelfrey neon-serde2 is a fork of neon-serde that has been updated for the latest Neon versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants