Update Python dependencies (main) (major) #1026
Open
Conversation
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
renovate
bot
requested review from
dragomirp,
marceloneppel and
taurus-forever
and removed request for
a team
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
added
the
Libraries: Out of sync
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1026 +/- ##
=======================================
Coverage 73.34% 73.34%
=======================================
Files 15 15
Lines 3916 3916
Branches 574 574
=======================================
Hits 2872 2872
Misses 830 830
Partials 214 214 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
taurus-forever
requested changes
Jul 15, 2025
Contributor
taurus-forever
left a comment
taurus-forever
left a comment
There was a problem hiding this comment.
IMHO PG14 will stay on ops 2 for a while
renovate
bot
force-pushed
the
renovate/main-major-python-dependencies
branch
from
84cfe12 to
d6bd798
Compare
renovate
bot
force-pushed
the
renovate/main-major-python-dependencies
branch
2 times, most recently
from
fb8708b to
16e406a
Compare
renovate
bot
force-pushed
the
renovate/main-major-python-dependencies
branch
2 times, most recently
from
0395f60 to
45ed270
Compare
renovate
bot
force-pushed
the
renovate/main-major-python-dependencies
branch
from
45ed270 to
d35853d
Compare
renovate
bot
force-pushed
the
renovate/main-major-python-dependencies
branch
from
d35853d to
b419de8
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/main-major-python-dependencies
branch
from
b419de8 to
47b5ada
Compare
renovate
bot
force-pushed
the
renovate/main-major-python-dependencies
branch
from
47b5ada to
c6e63b1
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/main-major-python-dependencies
branch
from
c6e63b1 to
f7ad02f
Compare
renovate
bot
force-pushed
the
renovate/main-major-python-dependencies
branch
from
f7ad02f to
e2fcf67
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/main-major-python-dependencies
branch
from
e2fcf67 to
e9266ad
Compare
renovate
bot
force-pushed
the
renovate/main-major-python-dependencies
branch
from
e9266ad to
21c4ef4
Compare
renovate
bot
force-pushed
the
renovate/main-major-python-dependencies
branch
from
21c4ef4 to
92b0556
Compare
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.
This PR contains the following updates:
2.23.1->3.4.0^2.23.1->^3.4.0^8.4.2->^9.0.2Release Notes
canonical/operator (ops)
v3.4.0Compare Source
Breaking Changes
Features
Fixes
ops.Pebble.pullcleans up temporary files if it errors (#2087)Documentation
simpleCharmcraft profile (#2138)Tests
Refactoring
CI
v3.3.1: : fix loading the Juju machine IDCompare 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.JujuContextandtesting.Context) is changed frominttostr, so some code or tests may need to be adjusted to use the correct type.What's Changed
Fixes
Full Changelog: canonical/operator@3.3.0...3.3.1
v3.3.0Compare Source
Features
Fixes
Documentation
CI
v3.2.0Compare Source
Features
Documentation
Layerinstead of aLayerDictin the httpbin charm (#2003)CI
v3.1.0Compare Source
Features
Fixes
Documentation
opsversion in Charmcraft profiles (#1872)Tests
CI
v3.0.0Compare Source
The minimum version of Python for Ops 3.x is 3.10.
Documentation
CI
pytest-dev/pytest (pytest)
v9.0.2Compare Source
pytest 9.0.2 (2025-12-06)
Bug fixes
#13896: The terminal progress feature added in pytest 9.0.0 has been disabled by default, except on Windows, due to compatibility issues with some terminal emulators.
You may enable it again by passing
-p terminalprogress. We may enable it by default again once compatibility improves in the future.Additionally, when the environment variable
TERMisdumb, the escape codes are no longer emitted, even if the plugin is enabled.#13904: Fixed the TOML type of the
tmp_path_retention_countsettings in the API reference from number to string.#13946: The private
config.inicfgattribute was changed in a breaking manner in pytest 9.0.0.Due to its usage in the ecosystem, it is now restored to working order using a compatibility shim.
It will be deprecated in pytest 9.1 and removed in pytest 10.
#13965: Fixed quadratic-time behavior when handling
unittestsubtests in Python 3.10.Improved documentation
pytest's command-line flags <command-line-flags>.v9.0.1Compare Source
pytest 9.0.1 (2025-11-12)
Bug fixes
raise unittest.SkipTest.Packaging updates and notes for downstreams
version string can be passed into its
package_envthroughthe
SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTESTenvironmentvariable as a part of the release process -- by
webknjaz.Contributor-facing changes
creating GitHub Releases without having a Git checkout on
disk -- by
bluetechandwebknjaz.version string can be passed into its
package_envthroughthe
SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTESTenvironmentvariable as a part of the release process -- by
webknjaz.v9.0.0Compare 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:
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.subTestis now also supported.This feature was originally implemented as a separate plugin in pytest-subtests, but since then has been merged into the core.
#13743: Added support for native TOML configuration files.
While pytest, since version 6, supports configuration in
pyproject.tomlfiles 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.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 usepytest.tomlor.pytest.toml:The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface.
See
config file formatsfor full details.#13823: Added a "strict mode" enabled by the
strictconfiguration option.When set to
true, thestrictoption currently enablesstrict_configstrict_markersstrict_parametrization_idsstrict_xfailThe individual strictness options can be explicitly set to override the global
strictsetting.The previously-deprecated
--strictcommand-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 modefor more details.#13737: Added the
strict_parametrization_idsconfiguration 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:
-p no:terminalprogresson the command line or via an environment variablePYTEST_ADDOPTS='-p no:terminalprogress'.addopts = "-p no:terminalprogress".#478: Support PEP420 (implicit namespace packages) as --pyargs target when
consider_namespace_packagesis true in the config.Previously, this option only impacted package imports, now it also impacts tests discovery.
#13678: Added a new
faulthandler_exit_on_timeoutconfiguration 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
aliasesparameter inParser.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.inifile andpyproject.tomlwith 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
--versionno longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version.Passing
--versiontwice (e.g.,pytest --version --version) retains the original behavior, showing both the pytest version and plugin information.#13823: Added
strict_xfailas an alias to thexfail_strictoption,strict_configas an alias to the--strict-configflag,and
strict_markersas an alias to the--strict-markersflag.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:
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
PytestRemovedIn9Warningnow generate errorsinstead of warning messages by default.
The affected features will be effectively removed in pytest 9.1, so please consult the
deprecationssection in the docs for directions on how to update existing code.In the pytest
9.0.Xseries, it is possible to change the errors back into warnings as astopgap measure by adding this to your
pytest.inifile:But this will stop working when pytest
9.1is released.If you have concerns about the removal of a specific feature, please add a
comment to
13779.Deprecations (removal in next major release)
monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend>now issues a deprecation warning when the prepended path contains legacy namespace packages (those usingpkg_resources.declare_namespace()).Users should migrate to native namespace packages (
420).See
monkeypatch-fixup-namespace-packagesfor details.Bug fixes
#13445: Made the type annotations of
pytest.skipand friends more spec-complaint to have them work across more type checkers.#13537: Fixed a bug in which
ExceptionGroupwith onlySkippedexceptions 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 aspytest x.py. This is now a usage error.#13722: Fixed a misleading assertion failure message when using
pytest.approxon mappings with differing lengths.#13773: Fixed the static fixture closure calculation to properly consider transitive dependencies requested by overridden fixtures.
#13816: Fixed
pytest.approxwhich now returns a clearer error message when comparing mappings with different keys.#13849: Hidden
.pytest.inifiles 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
pytesterin subprocess mode ignored all :attr`pytester.plugins <pytest.Pytester.plugins>` except the first.Fixed
pytesterin subprocess mode silently ignored non-strpytester.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
iniconfigandpackagingwere bumped to1.0.1and22.0.0, respectively.Contributor-facing changes
lsofcommand hanging (e.g. due to unreachable network filesystems), with the affected selftests being skipped after 10 seconds.gh pr newcommand inscripts/prepare-release-pr.py.The script now uses
gh pr createwhich is compatible with GitHub CLI v2.0+.ogrisel.tox>=4is now required when contributing to pytest.pytest_addoption(),pytest_configure(), andcacheshow()functions incacheprovider.py.Miscellaneous internal changes
-o/--override-ini) are now processed during startup rather than duringconfig.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.
This PR was generated by Mend Renovate. View the repository job log.