Repository navigation
Update all non-major dependencies - #998
Merged
Merged
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
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
v4.7.0→v4.8.06.170.11→6.170.159.17.1→9.18.14.6.4→4.6.60.68.0→0.68.13.1.0→3.1.19.1.1→9.2.0Release Notes
docker/login-action
v4.8.0Compare Source
Full Changelog: docker/login-action@v4.7.0...v4.8.0
HypothesisWorks/hypothesis (hypothesis)
v6.170.15: Hypothesis version 6.170.15Compare Source
Hypothesis now has 100% type coverage of our public API, as checked by
pyrefly.
The canonical version of these notes (with links) is on readthedocs.
v6.170.14: Hypothesis version 6.170.14Compare Source
This patch adjusts coverage settings for new dependencies; there is no
user-visible change.
The canonical version of these notes (with links) is on readthedocs.
v6.170.13: Hypothesis version 6.170.13Compare Source
This patch fixes the codemod for deprecated "characters()" arguments,
which previously raised an error when "**kwargs" were also passed.
The canonical version of these notes (with links) is on readthedocs.
v6.170.12: Hypothesis version 6.170.12Compare Source
This patch reduces Hypothesis' overhead for each test case. For simple
properties and strategies, generating test cases takes up to a third
less time and shrinking failing examples is up to twice as fast; most
tests will see a smaller improvement. "import hypothesis" is also
about 20% faster.
The canonical version of these notes (with links) is on readthedocs.
ipython/ipython (ipython)
v9.18.1Compare Source
v9.18.0Compare Source
jupyterlab/jupyterlab (jupyterlab)
v4.6.6Compare Source
4.6.6
(Full Changelog)
Bugs fixed
=and-lines inside$$math in the table of contents #19818 (@Yagnik-Trivedi)Maintenance and upkeep improvements
.yarn-state.yml#20332 (@krassowski)Documentation improvements
Contributors to this release
The following people contributed discussions, new ideas, code and documentation contributions, and review.
See our definition of contributors.
(GitHub contributors page for this release)
@aeodice21 (activity) | @chrikrah (activity) | @Darshan808 (activity) | @DebankurPaul (activity) | @dturaev (activity) | @Eapp1e (activity) | @jtpio (activity) | @krassowski (activity) | @KUMAR-AKASH-M (activity) | @lowgame (activity) | @MahathirMohammadShuvo (activity) | @minwookshin (activity) | @Mrun25 (activity) | @Parth-ui-commits (activity) | @r0c0y (activity) | @Yagnik-Trivedi (activity) | @Yash990-bit (activity)
v4.6.5Compare Source
4.6.5
(Full Changelog)
Bugs fixed
@codemirror/viewto 6.43.15, fixing text loss when typing with dead keys #20302 (@dturaev)disabledon default keyboard shortcuts in the JSON Settings Editor #20169 (@paulmromer)Maintenance and upkeep improvements
release-test: do not use conda #20179 (@krassowski)@yarnpkg/coreto fix the deduplicate script #19807 (@jtpio)Documentation improvements
Other merged PRs
ISectionEntry.iddocumentation #19967 (@jtpio)Contributors to this release
The following people contributed discussions, new ideas, code and documentation contributions, and review.
See our definition of contributors.
(GitHub contributors page for this release)
@brichet (activity) | @chanellebingham (activity) | @Darshan808 (activity) | @dturaev (activity) | @faysou (activity) | @irontaek (activity) | @jtpio (activity) | @krassowski (activity) | @MUFFANUJ (activity) | @nina-mir (activity) | @paulmromer (activity) | @pjdoland (activity) | @SatyamKumarCS (activity) | @x0Lazarus (activity) | @xuezhongyu01 (activity) | @Yagnik-Trivedi (activity) | @Yann-P (activity) | @Yash990-bit (activity)
pandas-dev/pandas (pandas)
v3.1.1: pandas 3.1.1Compare Source
We are pleased to announce the release of pandas 3.1.1.
This is a patch release in the 3.1.x series and includes some regression fixes and bug fixes. We recommend that all users of the 3.1.x series upgrade to this version.
See the full whatsnew for a list of all the changes.
The release can be installed from PyPI:
Or from conda-forge
Please report any issues with the release on the pandas issue tracker.
Thanks to all the contributors who made this release possible.
pytest-dev/pytest (pytest)
v9.2.0Compare Source
pytest 9.2.0 (2026-10-27)
Removals and backward incompatible breaking changes
#14716:
-cnow raises a usage error for a path that does not exist, is a directory, or is in a format pytest has no loader for. Such paths were previously either ignored or reported as an unhandledFileNotFoundError.#8593: The
indirect,idsandscopearguments ofMetafunc.parametrize() <pytest.Metafunc.parametrize>-- and therefore of@pytest.mark.parametrize <pytest.mark.parametrize ref>-- are now keyword-only.Passing them positionally was a common source of confusing errors, e.g.
parametrize("arg1", "arg2", [(1, 2)])made the argvalues land inindirectand failed withindirect fixture '(1, 2)' doesn't exist; such mistakes now fail with an understandableTypeError. The type annotations have always declared these arguments as keyword-only.#993: Plugin import failures at startup are now reported and classified instead of escaping as a raw traceback with the accidental exit code
1:-p,pytest_pluginsorPYTEST_PLUGINS-- exits withpytest.ExitCodeUSAGE_ERROR(4), like aconftest.pythat fails to import;pytest11entry point or a missing plugin dependency -- exits withpytest.ExitCodeINTERNAL_ERROR(3), with the traceback preserved.pytest.mainnow returns these codes instead of raisingImportError. Also fixed anIndexErrorfrom pytest's own internals when the plugin raised an exception with no arguments.Deprecations (removal in next major release)
#14742: The private
_pytest.python.CallSpec2name has been renamed toCallSpec.The old
CallSpec2alias remains available for now and will be removed in pytest 10 or 11.#14755: Schedule yield_fixture decorator for removal in pytest 10 or 11.
#14774: Similarly to the deprecation of class-scoped fixtures defined as instance methods in pytest 9.1,
all higher-scoped fixtures (
module,package, andsession) definedas instance methods are now deprecated.
They suffer from the same issue the original deprecation only fixed for
class-scoped fixtures, see
10819and14011.#14808: Passing a non-string value to a
string-typed ini option now emits apytest.PytestRemovedIn10Warning. This affects[tool.pytest.ini_options]inpyproject.toml. In pytest 10 this will raise aTypeError, matching the behavior of the corresponding TOML config path.#7323: Passing
bytestoTerminalReporter.write_line()is now deprecated, pass astrinstead.New features
strict_markersis enabled, marker names used in-mexpressions are now validated against registered markers.parametrize_long_str_id_strategyconfiguration option to control how longstr/bytesparameter values are handled in auto-generated test IDs. Explicit IDs set viaids=[...]orpytest.param(..., id=...)are not affected. Available strategies:short(default, values over 100 chars fall back toargname+index),sha256(SHA-256 hex digest),legacy(keep full value), anddisallow(error requesting explicit IDs).Improvements in existing functionality
#10745: A
RecursionErrorwhose recursion origin cannot be located now shows only thefirst and last 10 stack frames, matching what pytest already did when locating
the origin failed outright. Previously the full traceback -- often around a
thousand near-identical frames -- was rendered, which was both slow and
unreadable. Pass
--full-traceto see every frame.#10745: The line numbers of a module's statements are now computed once per traceback
instead of once per traceback entry, which noticeably speeds up rendering
failures raised from large test modules.
#11418: The cached rewritten modules in
__pycache__are now invalidated by a hash ofthe source instead of its modification time, using the checked-hash pyc format
from
552.Timestamps make the cache useless wherever source files get fresh modification
times, most notably in CI: a checkout gives every file a new mtime, so a
restored cache is discarded in full and every test module is rewritten again.
Hashing the source costs roughly 15 microseconds per file and makes the cache
survive that.
Existing timestamp based caches are ignored and rewritten once.
#12624: The
pytest_pluginsvariable and thePYTEST_PLUGINSenvironment variable now also accept entry point names of installed plugins (e.g.xdist), in addition to importable module names, matching the behavior of the-pcommand-line option.As part of this change, plugins specified by entry point name through these mechanisms are now also listed in the
plugins:line of the terminal header (12615).Based on the original implementation by Marcel Telka in
12616.#12697: Warnings emitted while importing plugins through
-p,PYTEST_PLUGINS, or entry point autoloading are now captured, filtered, and reported like other warnings.#12860: Assertion diffs for
dict.items()anddict.keys()comparisons (>=,<=,>,<,==) now show which items are missing, the same way set comparisons do.#13354:
Node.get_closest_marker <_pytest.nodes.Node.get_closest_marker>now also accepts a~pytest.MarkDecoratoras itsdefault, for exampleitem.get_closest_marker("foo", pytest.mark.foo(1)), and returns the wrapped~pytest.Mark.Previously the only way to build a
defaultwas to instantiate~pytest.Markdirectly, which is private and warns.#13369: Improved the error from
pytest.RunResult.assert_outcomeswhen a plugin changes or removes pytest's standard terminal summary, and documented how to isolate output-changing plugins.#13431: Exposed
pytest.ParameterSetas the type of the return value ofpytest.param().This can be used in type annotations and
isinstancechecks.#13564: Issue a warning when fixtures are wrapped with a decorator that prevents
correct discovery, including
@classmethodabove@pytest.fixtureand@staticmethodabove@pytest.fixture. Put@pytest.fixtureabovethose decorators on test classes.
#14164: Exposed
pytest.Approxas the type of the return value ofpytest.approx().This can be used in type annotations and
isinstancechecks.#14463: Assertion diffs for mappings now match up keys the way the compared mappings match them themselves.
Key comparison goes through the mappings' key views instead of plain sets of their keys, so a mapping
with its own notion of key equivalence, such as case-insensitive header mappings, no longer
reports its common keys as missing on either side.
#14523: Large assertion comparison diffs are now built lazily and capped to the
truncation budget, so a huge diff is no longer formatted in full just to
be truncated. As a consequence, the truncation footer no longer
reports the exact number of hidden lines.
#14687: The default fd-level output capturing (
--capture=fd) now skips reading the capture buffer for tests which produce no output, reducing per-test overhead in large test suites.#14724:
--no-summarynow only applies directly to pytest's own summary.The flag no longer skips the
pytest_terminal_summaryhook, so third-partyplugins (for example coverage) can still write their terminal summaries.
#14751:
parser.addini <pytest.Parser.addini>now also accepts type expressions for itstypeargument, in addition to the existing string tags: the plain Python typesstr,bool,int,float, aLiteralof strings, and unions of these (for exampleint | strorint | Literal["auto"]).#14754:
pytest.approx()now rejects infinite relative tolerances fordatetime.timedeltavalues with a clearValueErrorinstead of raisingOverflowError.#14791: The
junit_family,junit_logging,junit_duration_report,console_output_style,empty_parameter_set_mark,assertion_text_diff_styleandtmp_path_retention_policyconfiguration options are now registered with the set of values they accept: an invalid value now fails with a clean usage error instead of being silently ignored or crashing later, andpytest --helplists the accepted values.config.getini <pytest.Config.getini>now raisespytest.UsageErrorinstead ofTypeErrororValueErrorwhen the value read from the configuration file does not match the registered type, so a bad value is always reported as a short usage error message instead of an internal error traceback. Asking for an option name that was never registered still raisesValueError.#15006:
pytest.approxnow emitspytest.PytestApproxDecimalToleranceWarningwhen arelorabstolerance is given as afloatthat cannot be represented exactly for a~decimal.Decimalcomparison, since such a tolerance is widened to the float's exact binary value.#14675, #14953, #15153, #15132: The
truncation_limit_lines,truncation_limit_chars,max_warnings,verbosity_assertions,verbosity_test_cases,verbosity_subtests,tmp_path_retention_count,log_level,log_cli_level,log_file_level,log_auto_indentandfaulthandler_timeoutconfiguration options now accept native integer (and, forlog_auto_indent, boolean) values in TOML configuration files, while still accepting strings for backward compatibility.log_file_modenow reports invalid values as a usage error.#15254:
tmp_pathandTempPathFactory.mktemp <pytest.TempPathFactory.mktemp>no longer list the whole base temporary directory on every call, which made sessions with many temporary directories quadratically slow. Numbers are now handed out from a per-prefix counter, skipping names that already exist.#4569:
Node.add_marker <_pytest.nodes.Node.add_marker>now stores a~pytest.Markinnode.keywords, matching what marks applied during collection store. Previously it stored a~pytest.MarkDecorator.#9436: Avoided formatting tracebacks for tests marked with
xfail(run=False).Bug fixes
#10128: Configured warning filters now apply to warnings emitted by
pytest_configurehooks.#10210:
pytest.approxnow raises aTypeErrorfor any nested container, notonly for one of the same type as its parent. Previously
approx([{"k": 1}])and
approx({"k": [1]})were accepted and then compared unequal to everyvalue, silently ignoring the tolerance, while
approx([[1]])correctlyreported that nesting is unsupported.
#10644:
monkeypatch.setattr()no longer leaves a new entry in the instance__dict__when it patches an attribute that the instance inherits from its class.Previously
undo()assigned the inherited value onto the instance, which shadowed the class attribute -- permanently freezing the result for descriptors that resolve dynamically.#1139: Fixed tracebacks showing
???instead of source lines for code compiled with a filename relative to a directory other than the current working directory -- e.g. compiled Cython modules, when running pytest from a subdirectory of the project root.The source lookup now falls back to searching
sys.pathfor such filenames, as the standardtracebackmodule does.#11502: The
rootdiris no longer derived from a configuration file that is not a regular file, such as--config-file=/dev/null.#11783: Plugins installed in editable mode (
660) are marked for assertion rewriting again.Such installs do not record the package's Python files in the distribution metadata, so pytest found nothing to rewrite and assertions inside the plugin lost their introspection. The plugin's entry point is now used to locate the package in that case.
#11933:
pytest.warnsno longer re-emits unmatched warnings withmodule="warnings", which causedmodule-based warning filters to be applied to the wrong warnings. Sincewarnings.WarningMessagedoes not record the module a warning was emitted with, re-emitted warnings now use the standardwarnings.warn_explicitdefault of deriving the module from the warning's filename.#12175:
ExceptionInfo.exconly(tryshort=True) <pytest.ExceptionInfo.exconly>now strips theAssertionError:prefix of failedassertstatements for~pytest.ExceptionInfoobjects created bypytest.raises, and failures insideunittest.TestCase.subTestreport the same short crash line as regular tests.#12223: The
messageattribute of<failure>and<error>elements in--junitxmlreports is now shortened to whole lines within 500 characters. When something is dropped, it ends with a note pointing to the element text, which still holds the full report. Previously, very verbose assertion output (e.g. with-vv) produced attributes tens of thousands of characters long, which some XML parsers fail on.#12307: Fixed truncation of long collections (lists, dicts, sets, etc.) in the "message" part of failed assertions (as in
assert condition, msg) when using-vv: the message now uses the same unlimited repr as the rest of the assertion output, instead of eliding collection elements with....#12824: Custom command-line options now fail with a clear error when their implicit
destination conflicts with an existing option, avoiding silent overrides of
built-in options such as
-k.#13292: Fixed a stale rewritten module being used when a test file is modified twice
within the same second without changing its size -- the pyc header could only
record whole-second timestamps. The cache is now keyed on a hash of the source.
#14036:
__tracebackhide__is now respected inExceptionGrouptracebacks, both for the group itself and for its sub-exceptions.#14189: Nested usage of
caplog.filtering <pytest.LogCaptureFixture.filtering>no longer removes filters early if they were already present.#14412: Fixed incorrect timing information for subtests and parent tests when
console_output_style = "times".#14445: Assertion rewriting no longer evaluates walrus operator (
:=) expressions more than once, which reported results the test never computed when the expression had side effects.An operand evaluated before a later walrus is now reported with the value it actually saw, so
assert value != identity(value := value.lower())keeps Python's left-to-right order.#14552: Fixed stale
co_filenamevalues after a test module or directory is moved. Assertion-rewrite caches are reused when the source hash still matches, and in-memory code objects are pointed at the current path.Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.