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.

Sign up for GitHub

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

Jump to bottom

Document or Improve the way to force the workflow to install a specific tox version. #92

Open
pllim opened this issue Dec 7, 2022 · 5 comments
Open

Document or Improve the way to force the workflow to install a specific tox version. #92

pllim opened this issue Dec 7, 2022 · 5 comments

Comments

@pllim
Copy link
Contributor

pllim commented Dec 7, 2022

tox 4.0.0 came out and things broke. Do you test against dev or pre-release version of tox?

Also see tox-dev/tox#2612
@pllim
Copy link
Contributor Author

pllim commented Dec 7, 2022

Also see https://tox.wiki/en/latest/faq.html#breaking-changes-in-tox-4

@Cadair
Copy link
Member

Cadair commented Dec 7, 2022

This repo hasn't broken when tox 4 came out, what broke was the fact all the repos using it had a config file which was incompatible with tox 4 ;)

@pllim
Copy link
Contributor Author

pllim commented Dec 7, 2022

But is there a way for downstream to ask this workflow to use dev tox or pre-release tox?

@Cadair
Copy link
Member

Cadair commented Dec 7, 2022

Well the way we have pinned tox would also work. Would be good to document at least, and maybe make less hacky.

@Cadair Cadair changed the title Test against dev or pre-release tox ? Document or Improve the way to force the workflow to install a specific tox version. Dec 8, 2022
@Cadair Cadair mentioned this issue Dec 8, 2022
Closed
@pllim
Copy link
Contributor Author

pllim commented Dec 9, 2022

Also please document how to install the pre-release of tox.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Cadair @pllim