Update Python dependencies (16/edge) (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ops (changelog)	2.23.1 -> 3.3.1
ops (changelog)	^2.23.1 -> ^3.3.1
pytest (changelog)	^8.4.2 -> ^9.0.1

---

Release Notes

canonical/operator (ops)

v3.3.1: : fix loading the Juju machine ID

Compare Source

This is a bug-fix release to fix an issue introduced in Ops 3.3.0 (in production) and Ops 3.2.0 (in testing), where loading the Juju machine ID would fail if the ID was not an integer.

The type of the machine ID (both in ops.JujuContext and testing.Context) is changed from int to str, so some code or tests may need to be adjusted to use the correct type.

What's Changed

Fixes

• Change JujuContext.machine_id from int to str (#​2108)

Full Changelog: canonical/operator@3.3.0...3.3.1

v3.3.0

Compare Source

Features

• Expose the Juju hook context in ops.JujuContext (#​1996)

Fixes

• In testing, separate relation data cache from mock Juju backend (#​2052)

Documentation

• Use uv for testing and packing the httpbin charm (#​2011)
• Improve intro to ops.testing reference (#​2023)
• In httpbin charm integration tests, add env var for charm file to deploy (#​2018)
• Update get_cloud_spec doc now that credential-get works on K8s (#​2031)
• Note that arbitrary_types_allowed is required when ops.Secret is used in a Pydantic class (#​2038)
• Clean up Resources.fetch docstring, add ModelError exception (#​2039)
• Note that the peer databag isn't usable during the install event (#​2051)
• Fix testing code in actions how-to guide (#​2054)

CI

• Nicer logging output in the release script using rich (#​2017)
• Clean up PYTHONPATH in tox.ini (#​2058)

v3.2.0

Compare Source

Features

• Add security event logging (#​1905)
• Surface JUJU_MACHINE_ID envvar in testing env (#​1961)
• Add a new log target type opentelemetry (#​1937)

Documentation

• Update links and config for switch to documentation.ubuntu.com/ops (#​1940)
• Update the required Python version and note the 2.x documentation site (#​1946)
• Be consistent with recommending self.config (#​1947)
• Use latest styles from starter pack and remove .html extensions (#​1951)
• Remove .html extensions from hardcoded links (#​1955)
• Fix broken URLs in sitemap (#​1956)
• Add related doc links to homepage (#​1959)
• Use classes from ops instead of ops. (#​1968)
• Fix unstyled error pages (#​1969)
• Add Google Analyics integration and cookie consent banner (#​1971)
• Refresh docs homepage with more context about Ops (#​1964)
• Update link to Charmlibs docs (#​1985)
• Remove unnecessary pages from sitemap (#​1979)
• Update the httpbin example charm to Jubilant (#​1987)
• Update the Zero to Hero tutorial to Jubilant (#​1988)
• Add model-config best practice note (#​1990)
• Change some best practices to tips (#​2001)
• Add integration test for invalid config in httpbin charm (#​2002)
• Make a Layer instead of a LayerDict in the httpbin charm (#​2003)
• Update how-to to feature Jubilant (#​2000, #​2004)
• Use Charmcraft-style format and lint for example charms, not Ops-style (#​2008)
• Update broken link to HookVars source code (#​2006)

CI

• Fixes for the SBOM and security scan workflow, and trigger it on publishing (#​1916)
• Store the charmcraft logs if packing fails (#​1936)
• Install release dependencies for the TIOBE analysis (#​1930)
• Add Juju 4/beta to the smoke test matrix (#​1963)
• Adjust permissions block in publish workflow (#​1984)
• Update actions/checkout to v5 (#​1993)
• Enable doctests (#​1991)
• Ignore juju/4 timeouts (#​1998)
• Remove the token for SBOM and security scan workflow (#​2009)
• Speed up integration test (#​1978)

v3.1.0

Compare Source

Features

• Release automation script (#​1855)
• Add app_name and unit_id attributes to testing.context (#​1920)

Fixes

• If an event ends with _abort(0) tests should behave as if it ended successfully (#​1887)
• If self.app is not actually set avoid a new crash location (#​1897)
• Only add the remote unit for departed and broken relation events, fix ordering (#​1918)
• Add the remote unit to relation.data but not relation.units (#​1925)

Documentation

• Use load_config in the httpbin example charm (#​1852)
• Update HACKING.md with how to bump ops version in Charmcraft profiles (#​1872)
• Change title of docs site (#​1890)
• Use config and action classes in the Kubernetes tutorial (#​1891)
• Reference example charms from K8s tutorial and fix consistency (#​1898)
• Update style guide (#​1720)
• Fix issues in how-to guide for stored state (#​1901)
• Link out to the 12-factor tutorials from the tutorial index page (#​1902)
• Replace broken link in testing explanation (#​1913)
• Expand the storage how-to with content from Juju docs scheduled for removal (#​1915)
• Ops tracing how to (#​1853)
• Add a security explanation doc (#​1904)

Tests

• Replace Python version to 3.10 for observability charm tests (#​1914)

CI

• Use httpbin demo charm for the Charmcraft pack test (#​1895)
• Move TIOBE workflow to self-hosted runners (#​1912)
• Add SBOM generation and secscan workflow (#​1906)
• Build and publish in one step (#​1857)
• Update the name and email when updating the charm pins (#​1924)
• Drop smoke test against 20.04 (#​1923)

v3.0.0

Compare Source

The minimum version of Python for Ops 3.x is 3.10.

Documentation

• Be consistent with recommending self.app and self.unit (#​1856)

CI

• Hotfix, publish job for ops-tracing (#​1865)

pytest-dev/pytest (pytest)

v9.0.1

Compare Source

pytest 9.0.1 (2025-11-12)

Bug fixes

• #​13895: Restore support for skipping tests via raise unittest.SkipTest.
• #​13896: The terminal progress plugin added in pytest 9.0 is now automatically disabled when iTerm2 is detected, it generated desktop notifications instead of the desired functionality.
• #​13904: Fixed the TOML type of the verbosity settings in the API reference from number to string.
• #​13910: Fixed UserWarning: Do not expect file_or_dir on some earlier Python 3.12 and 3.13 point versions.

Packaging updates and notes for downstreams

• #​13933: The tox configuration has been adjusted to make sure the desired
  version string can be passed into its package_env through
  the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment
  variable as a part of the release process -- by webknjaz.

Contributor-facing changes

• #​13891, #​13942: The CI/CD part of the release automation is now capable of
  creating GitHub Releases without having a Git checkout on
  disk -- by bluetech and webknjaz.
• #​13933: The tox configuration has been adjusted to make sure the desired
  version string can be passed into its package_env through
  the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment
  variable as a part of the release process -- by webknjaz.

v9.0.0

Compare Source

pytest 9.0.0 (2025-11-05)

New features

• #​1367: Support for subtests has been added.

  subtests <subtests> are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time.

  Example:

  def contains_docstring(p: Path) -> bool:
      """Return True if the given Python file contains a top-level docstring."""
      ...
  
  def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:
      for path in Path.cwd().glob("*.py"):
          with subtests.test(path=str(path)):
              assert contains_docstring(path)

  Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring.

  In addition, unittest.TestCase.subTest is now also supported.

  This feature was originally implemented as a separate plugin in pytest-subtests, but since then has been merged into the core.

  [!NOTE]
  This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable.

• #​13743: Added support for native TOML configuration files.

  While pytest, since version 6, supports configuration in pyproject.toml files under [tool.pytest.ini_options],
  it does so in an "INI compatibility mode", where all configuration values are treated as strings or list of strings.
  Now, pytest supports the native TOML data model.

  In pyproject.toml, the native TOML configuration is under the [tool.pytest] table.

  # pyproject.toml
  [tool.pytest]
  minversion = "9.0"
  addopts = ["-ra", "-q"]
  testpaths = [
      "tests",
      "integration",
  ]

  The [tool.pytest.ini_options] table remains supported, but both tables cannot be used at the same time.

  If you prefer to use a separate configuration file, or don't use pyproject.toml, you can use pytest.toml or .pytest.toml:

  # pytest.toml or .pytest.toml
  [pytest]
  minversion = "9.0"
  addopts = ["-ra", "-q"]
  testpaths = [
      "tests",
      "integration",
  ]

  The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface.

  See config file formats for full details.

• #​13823: Added a "strict mode" enabled by the strict configuration option.

  When set to true, the strict option currently enables

  • strict_config
  • strict_markers
  • strict_parametrization_ids
  • strict_xfail

  The individual strictness options can be explicitly set to override the global strict setting.

  The previously-deprecated --strict command-line flag now enables strict mode.

  If pytest adds new strictness options in the future, they will also be enabled in strict mode.
  Therefore, you should only enable strict mode if you use a pinned/locked version of pytest,
  or if you want to proactively adopt new strictness options as they are added.

  See strict mode for more details.

• #​13737: Added the strict_parametrization_ids configuration option.

  When set, pytest emits an error if it detects non-unique parameter set IDs,
  rather than automatically making the IDs unique by adding 0, 1, ... to them.
  This can be particularly useful for catching unintended duplicates.

• #​13072: Added support for displaying test session progress in the terminal tab using the OSC 9;4; ANSI sequence.
  When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,
  you'll see the progress in the terminal tab or window,
  allowing you to monitor pytest's progress at a glance.

  This feature is automatically enabled when running in a TTY. It is implemented as an internal plugin. If needed, it can be disabled as follows:

  • On a user level, using -p no:terminalprogress on the command line or via an environment variable PYTEST_ADDOPTS='-p no:terminalprogress'.
  • On a project configuration level, using addopts = "-p no:terminalprogress".

• #​478: Support PEP420 (implicit namespace packages) as --pyargs target when consider_namespace_packages is true in the config.

  Previously, this option only impacted package imports, now it also impacts tests discovery.

• #​13678: Added a new faulthandler_exit_on_timeout configuration option set to "false" by default to let faulthandler interrupt the pytest process after a timeout in case of deadlock.

  Previously, a faulthandler timeout would only dump the traceback of all threads to stderr, but would not interrupt the pytest process.

  -- by ogrisel.

• #​13829: Added support for configuration option aliases via the aliases parameter in Parser.addini() <pytest.Parser.addini>.

  Plugins can now register alternative names for configuration options,
  allowing for more flexibility in configuration naming and supporting backward compatibility when renaming options.
  The canonical name always takes precedence if both the canonical name and an alias are specified in the configuration file.

Improvements in existing functionality

• #​13330: Having pytest configuration spread over more than one file (for example having both a pytest.ini file and pyproject.toml with a [tool.pytest.ini_options] table) will now print a warning to make it clearer to the user that only one of them is actually used.

  -- by sgaist

• #​13574: The single argument --version no longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version.

  Passing --version twice (e.g., pytest --version --version) retains the original behavior, showing both the pytest version and plugin information.

  [!NOTE]
  Since --version is now processed early, it only takes effect when passed directly via the command line. It will not work if set through other mechanisms, such as PYTEST_ADDOPTS or addopts.

• #​13823: Added strict_xfail as an alias to the xfail_strict option,
  strict_config as an alias to the --strict-config flag,
  and strict_markers as an alias to the --strict-markers flag.
  This makes all strictness options consistently have configuration options with the prefix strict_.

• #​13700: --junitxml no longer prints the generated xml file summary at the end of the pytest session when --quiet is given.

• #​13732: Previously, when filtering warnings, pytest would fail if the filter referenced a class that could not be imported. Now, this only outputs a message indicating the problem.

• #​13859: Clarify the error message for pytest.raises() when a regex match fails.

• #​13861: Better sentence structure in a test's expected error message. Previously, the error message would be "expected exception must be <expected>, but got <actual>". Now, it is "Expected <expected>, but got <actual>".

Removals and backward incompatible breaking changes

• #​12083: Fixed a bug where an invocation such as pytest a/ a/b would cause only tests from a/b to run, and not other tests under a/.

  The fix entails a few breaking changes to how such overlapping arguments and duplicates are handled:

  1. pytest a/b a/ or pytest a/ a/b are equivalent to pytest a; if an argument overlaps another arguments, only the prefix remains.
  2. pytest x.py x.py is equivalent to pytest x.py; previously such an invocation was taken as an explicit request to run the tests from the file twice.

  If you rely on these behaviors, consider using --keep-duplicates <duplicate-paths>, which retains its existing behavior (including the bug).

• #​13719: Support for Python 3.9 is dropped following its end of life.

• #​13766: Previously, pytest would assume it was running in a CI/CD environment if either of the environment variables $CI or $BUILD_NUMBER was defined;
  now, CI mode is only activated if at least one of those variables is defined and set to a non-empty value.

• #​13779: PytestRemovedIn9Warning deprecation warnings are now errors by default.

  Following our plan to remove deprecated features with as little disruption as
  possible, all warnings of type PytestRemovedIn9Warning now generate errors
  instead of warning messages by default.

  The affected features will be effectively removed in pytest 9.1, so please consult the
  deprecations section in the docs for directions on how to update existing code.

  In the pytest 9.0.X series, it is possible to change the errors back into warnings as a
  stopgap measure by adding this to your pytest.ini file:

  [pytest]
  filterwarnings =
      ignore::pytest.PytestRemovedIn9Warning

  But this will stop working when pytest 9.1 is released.

  If you have concerns about the removal of a specific feature, please add a
  comment to 13779.

Deprecations (removal in next major release)

• #​13807: monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend> now issues a deprecation warning when the prepended path contains legacy namespace packages (those using pkg_resources.declare_namespace()).
  Users should migrate to native namespace packages (420).
  See monkeypatch-fixup-namespace-packages for details.

Bug fixes

• #​13445: Made the type annotations of pytest.skip and friends more spec-complaint to have them work across more type checkers.

• #​13537: Fixed a bug in which ExceptionGroup with only Skipped exceptions in teardown was not handled correctly and showed as error.

• #​13598: Fixed possible collection confusion on Windows when short paths and symlinks are involved.

• #​13716: Fixed a bug where a nonsensical invocation like pytest x.py[a] (a file cannot be parametrized) was silently treated as pytest x.py. This is now a usage error.

• #​13722: Fixed a misleading assertion failure message when using pytest.approx on mappings with differing lengths.

• #​13773: Fixed the static fixture closure calculation to properly consider transitive dependencies requested by overridden fixtures.

• #​13816: Fixed pytest.approx which now returns a clearer error message when comparing mappings with different keys.

• #​13849: Hidden .pytest.ini files are now picked up as the config file even if empty.
  This was an inconsistency with non-hidden pytest.ini.

• #​13865: Fixed --show-capture with --tb=line.

• #​13522: Fixed pytester in subprocess mode ignored all :attr`pytester.plugins <pytest.Pytester.plugins>` except the first.

  Fixed pytester in subprocess mode silently ignored non-str pytester.plugins <pytest.Pytester.plugins>.
  Now it errors instead.
  If you are affected by this, specify the plugin by name, or switch the affected tests to use pytester.runpytest_inprocess <pytest.Pytester.runpytest_inprocess> explicitly instead.

Packaging updates and notes for downstreams

• #​13791: Minimum requirements on iniconfig and packaging were bumped to 1.0.1 and 22.0.0, respectively.

Contributor-facing changes

• #​12244: Fixed self-test failures when TERM=dumb.
• #​12474: Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo documentation.
• #​13621: pytest's own testsuite now handles the lsof command hanging (e.g. due to unreachable network filesystems), with the affected selftests being skipped after 10 seconds.
• #​13638: Fixed deprecated gh pr new command in scripts/prepare-release-pr.py.
  The script now uses gh pr create which is compatible with GitHub CLI v2.0+.
• #​13695: Flush stdout and stderr in Pytester.run to avoid truncated outputs in test_faulthandler.py::test_timeout on CI -- by ogrisel.
• #​13771: Skip test_do_not_collect_symlink_siblings on Windows environments without symlink support to avoid false negatives.
• #​13841: tox>=4 is now required when contributing to pytest.
• #​13625: Added missing docstrings to pytest_addoption(), pytest_configure(), and cacheshow() functions in cacheprovider.py.

Miscellaneous internal changes

• #​13830: Configuration overrides (-o/--override-ini) are now processed during startup rather than during config.getini() <pytest.Config.getini>.

---

Configuration

📅 Schedule: Branch creation - Between 01:00 AM and 05:59 AM, only on Tuesday ( * 1-5 * * 2 ) in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.44%. Comparing base (48d4eb4) to head (759d9e9).
⚠️ Report is 7 commits behind head on 16/edge.

❌ Your project check has failed because the head coverage (67.44%) is below the target coverage (70.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@           Coverage Diff            @@
##           16/edge    #1027   +/-   ##
========================================
  Coverage    67.44%   67.44%           
========================================
  Files           18       18           
  Lines         3947     3947           
  Branches       564      564           
========================================
  Hits          2662     2662           
  Misses        1112     1112           
  Partials       173      173           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[taurus-forever]

IMHO PG16 will stay on ops 2 until we release the first 16/stable.