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

Introduce Upgrading doc page for tox4 #2805

Merged
merged 1 commit into from
Jan 2, 2023

Conversation

sirosen
Copy link
Contributor

@sirosen sirosen commented Jan 2, 2023

I wanted to contribute to some of the help:wanted docs issues, and picked #2728. However, it was not clear where this should go in the docs, and I think there are other issues related to tox4 changes which will have the same problem.
I am therefore proposing a new page in the docs, an upgrading guide, which covers the backwards-incompatible changes.

(Inspired by various bits of prior art, including the sqlalchemy 2.0 migration doc.)

If this doesn't seem like a good addition/direction for the docs, please feel free to close, and I'll try to make contributions within the existing structure instead.


This adds a new page to the docs, Upgrading, meant to remove the documentation regarding backwards incompatible changes in tox4 from the FAQ into a dedicated page.

The content of the page is primarily a lift-and-shift of the breaking changes section of the FAQ, and the FAQ page and Upgrading pages now cross-link to one another.

New content is added to the Upgrading page in the form of

  • a preamble for the doc
  • a section, "Legacy CLI entry point may result in ambiguous usages"

The new section resolves #2728

EDIT: I have removed part of this PR, indicated with strikethrough above.

Copy link
Member

@gaborbernat gaborbernat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, let's not merge two things into one. The migration to upgrade should be a separate PR.

This adds a new page to the docs, Upgrading, meant to remove
the documentation regarding backwards incompatible changes in tox4
from the FAQ into a dedicated page.

The content of the page is primarily a lift-and-shift of the breaking
changes section of the FAQ, and the FAQ page and Upgrading pages now
cross-link to one another.

New content is added to the Upgrading page in the form of a preamble
for the doc.
@sirosen
Copy link
Contributor Author

sirosen commented Jan 2, 2023

That's a very fair ask. I've removed the additional doc and struck-through parts of the PR comment above.
I also did a rebase because I was missing a change from main.

I'm happy to do a fresh PR if that's easier too.

@gaborbernat gaborbernat merged commit 031e902 into tox-dev:main Jan 2, 2023
@sirosen sirosen deleted the upgrading-doc branch January 3, 2023 00:31
descope bot referenced this pull request in descope/django-descope Jan 18, 2023
This PR contains the following updates:

| Package | Type | Update | Change | Pending |
|---|---|---|---|---|
| [tox](https://github.com/tox-dev/tox)
([changelog](https://tox.wiki/en/latest/changelog.html)) | dev | minor |
`4.1.3` -> `4.2.0` | `4.3.4` (+12) |

---

### Release Notes

<details>
<summary>tox-dev/tox</summary>

### [`v4.2.0`](https://github.com/tox-dev/tox/releases/tag/4.2.0)

[Compare Source](https://github.com/tox-dev/tox/compare/4.1.3...4.2.0)

#### What's Changed

- Introduce Upgrading doc page for tox4 by
[@&#8203;sirosen](https://github.com/sirosen) in
[https://github.com/tox-dev/tox/pull/2805](https://github.com/tox-dev/tox/pull/2805)
- Document ambiguous usages in v3-to-v4 by
[@&#8203;sirosen](https://github.com/sirosen) in
[https://github.com/tox-dev/tox/pull/2808](https://github.com/tox-dev/tox/pull/2808)
- Packaging inherits from pkgenv, deps and document tox 4 packaging
changes by [@&#8203;gaborbernat](https://github.com/gaborbernat) in
[https://github.com/tox-dev/tox/pull/2813](https://github.com/tox-dev/tox/pull/2813)

**Full Changelog**: tox-dev/tox@4.1.3...4.2.0

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC45OS4yIiwidXBkYXRlZEluVmVyIjoiMzQuOTkuMiJ9-->

Co-authored-by: descope[bot] <descope[bot]@users.noreply.github.com>
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.

tox4: Unable to run env called run
2 participants