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

Next release version #50

Closed
rth opened this issue Oct 16, 2022 · 2 comments · Fixed by #79
Closed

Next release version #50

rth opened this issue Oct 16, 2022 · 2 comments · Fixed by #79

Comments

@rth
Copy link
Member

rth commented Oct 16, 2022

There are a number of PRs that's going to be merged, so it would be good to tag soon.

The question is which version we should use. I don't think trying to keep with Pyodide versions would work, I would rather we followed semver and made this version evolve separately. Though we would still need to indicate the compatible Pyodide releases somehow.

WDYT?

@ryanking13
Copy link
Member

Yes, we have already released pytest-pyodide independently several times, so I think it is okay to have a separate version.

Though we would still need to indicate the compatible Pyodide releases somehow.

Maybe a short table that contains "this version of pytest-pyodide is tested with Pyodide v0.21.0, v0.20.0, ..." would work?

pytest-pyodide Tested Pyodide versions
0.22.0 0.21.0, 0.20.0
0.23.0 0.22.0, 0.21.0, 0.20.0
... ...

@rth
Copy link
Member Author

rth commented Nov 26, 2022

+1 to add that table to the readme.

@rth rth mentioned this issue Jan 3, 2023
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 a pull request may close this issue.

2 participants