Repository navigation
chore: drop pytest-operator and python-libjuju (2.23) - #2837
Merged
Merged
Conversation
Switch our smoke tests to `jubilant`... well Tony's jubilant-backports. Part of our efforts to move from pytest-operator to jubilant everywhere. CI Smoke: https://github.com/dimaqq/operator/actions/runs/16782556856 (cherry picked from commit f5197d4)
Now that we're using Jubilant rather than python-libjuju, we can smoke test against Juju 4 as well. The smoke test only packs (not relevant) and deploys, so it's not showing a great deal of what works/doesn't work in Juju 4, but it's worth knowing this little bit. [Passing run in my fork](https://github.com/tonyandrewmeyer/operator/actions/runs/16816761841). (cherry picked from commit b367505)
Part of the series "let's get rid of python-libjuju and pytest-operator and use jubilant instead" across our codebase. This PR updates the integration tests in the `httpbin-demo` example. (cherry picked from commit 736624c)
Doc preview: https://canonical-ubuntu-documentation-library--1988.com.readthedocs.build/ops/1988/ Check list: - [x] global `tox` - [x] k8s-1. `tox` - [x] k8s-1. `tox -e integration` - [x] k8s-2. `tox` - [x] k8s-2. `tox -e integration` - [x] k8s-3. `tox` - [x] k8s-3. `tox -e integration` - [x] k8s-4. `tox` - [x] k8s-4. `tox -e integration` - [x] k8s-5. `tox` - [x] k8s-5. `tox -e integration` (cherry picked from commit 815d5eb)
- add jubilant to intersphinx - update docs/howto/manage-the-workload-version.md to jubilant - update docs/howto/write-integration-tests-for-a-charm.md to jubilant (cherry picked from commit 18e95fe)
(cherry picked from commit 3c4cd3a) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
tonyandrewmeyer
marked this pull request as ready for review
October 21, 2026 18:52
dwilding
approved these changes
Oct 21, 2026
james-garner-canonical
approved these changes
Oct 21, 2026
james-garner-canonical
left a comment
Contributor
There was a problem hiding this comment.
Thanks, I didn't read all the changes thoroughly, but this looks structurally sound.
Backport of #1998, which was missed from the original cherry-pick list. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of the move from pytest-operator and python-libjuju to Jubilant, so that the 2.23 maintenance branch no longer depends on either.
Cherry-picked from main, in order:
jujudependency and add Juju 4 to the smoke matrix)Adjustments for the 2.x branch:
pyproject.tomlare kept, as is the 20.04 base in the smoke test parametrisation.ops-2.*.whlrather thanops-3.*.whl.uv.lockwas regenerated rather than merged, which drops pytest-operator, python-libjuju, pytest-asyncio and their transitive dependencies.docs/custom_conf.py, since this branch still has the older starter-pack layout.