Repository navigation
chore(deps): update all non-major dependencies - #169
Open
renovate-coveo[bot] wants to merge 1 commit into
Open
renovate-coveo[bot] wants to merge 1 commit into
renovate-coveo[bot] wants to merge 1 commit into
Conversation
renovate-coveo
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
October 5, 2026 20:07
158fcbd to
e4e44ea
Compare
renovate-coveo
Bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
October 15, 2026 08:07
9949aaf to
dd58843
Compare
renovate-coveo
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
October 23, 2026 08:08
cf1e0c0 to
a8d5143
Compare
renovate-coveo
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
October 26, 2026 18:13
b90e593 to
2b07245
Compare
renovate-coveo
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 27, 2026 19:06
2b07245 to
a024208
Compare
This branch has not been deployed
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.
This PR contains the following updates:
7.3.0→7.4.17.5.09.0.1→9.0.22.3.1→2.4.02.4.12.4.3→2.5.12.4.3→2.5.11.10.0→1.10.11.10.0→1.10.1v1.14.2→v1.14.3v2.21.1→v2.22.2v2.22.30.15.1→0.15.20.15.1→0.15.2[skip release]
Release Notes
pycqa/flake8 (flake8)
v7.4.1Compare Source
v7.4.0Compare Source
PyCQA/isort (isort)
v9.0.2Compare Source
🪲 Fixes
Other changes
processby @DanielNoord in #2677Full Changelog: PyCQA/isort@9.0.1...9.0.2
python/mypy (mypy)
v2.4.0Compare Source
python-poetry/poetry (poetry)
v2.5.1Compare Source
Fixed
installer.builtin-uninstallset failed with aTypeError(#11077).v2.5.0Compare Source
Added
installer.builtin-uninstallsetting to uninstall packages with a built-in uninstaller instead of invokingpip uninstall(#10931).Changed
httpsrepository viahttp(#11073).virtualenvs.createisfalse(#10941).poetry init(#10909).pyproject.tomlfile in the message about already present packages inpoetry add(#10908).#10896,
#10903,
#10949,
#10951,
#10953).
#10954).
#10958).
poetry searchfor single-token queries (#10906).requests(#11004).Fixed
KeyError(#11008).pyproject.tomlfile (#10987).developsetting changed (#11022).filewere not installed when installing the project (#10736).direct_url.jsonfor path dependencies (#10917).poetry show <package>showed a version that was not relevant for the current environment if there were multiple versions of the package in the lock file (#11003).poetry show --outdateddid not find newer versions of packages from sources withexplicitpriority (#10982).poetry env activateignored the environment that was determined by the application, e.g. when using--directory(#10916).poetry initproposed an invalid package name if the directory name was not a valid package name (#10975).Docs
--licenseoption ofpoetry initandpoetry new(#11064).poetry updatewith dependency groups (#11024).poetry runwith console scripts (#10984).--no-cachedisables (#10915).poetry self update(#10923).#10938,
#11000,
#11043).
poetry-core (
2.5.0)<Vversion constraint wrongly allowed pre-releases ofVin some cases (#939).!= <value>constraint was wrongly considered to allow all values of a<value> not inconstraint (#955).platform_releasemarkers with incompatible constraint types failed (#956).IndexError(#964).IndexError(#971).~=constraint was wrong for versions with more than three release segments (#973).python-poetry/poetry-plugin-export (poetry-plugin-export)
v1.10.1Compare Source
Fixed
pypa/gh-action-pypi-publish
v1.14.3Compare Source
Keeping the community safe is a collaborative effort! 💛💙
🛠️ Security Tightening
@webknjaz💰 made sure the dependency tree within the action runtime uses hash-checking from now on via #420.
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.14.2...v1.14.3
🧔♂️ Release Manager: @webknjaz 🇺🇦
💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.
step-security/harden-runner
v2.22.2Compare Source
What's Changed
Full Changelog: step-security/harden-runner@v2.22.1...v2.22.2
v2.22.1Compare Source
What's Changed
Full Changelog: step-security/harden-runner@v2.22.0...v2.22.1
v2.22.0Compare Source
What's Changed
Full Changelog: step-security/harden-runner@v2.21.1...v2.22.0
python-poetry/tomlkit (tomlkit)
v0.15.2Compare Source
Changed
\u001binstead of\e, which is only valid in TOML 1.1, so the output stays readable by TOML 1.0 parsers such astomllib. (#641)key_value()now raisesUnexpectedCharErroron anything other than whitespace or a comment after the pair, instead of silently discarding it (e.g.key_value("a = 1 b = 2")), matchingparse(). (#594)integer()given a string now validates it against the TOML integer grammar and keeps the original text, so grouping underscores (e.g.integer("1_000")) survivedumps(); strings that are not valid TOML integers (e.g."010") now raiseValueError. (#336)foldargument toDateTimeandTime, mirroring the stdlib, and carryfoldthroughitem(), arithmetic (including datetime subtraction) andunwrap(), so a folded local time no longer converts an hour off. (#619, #623, #626)[project]table; building from source now requirespoetry-core>=2.2.0. (#607, #609)Fixed
[a.b.c]then[a]withb.z = 1extends the implicita.bsuper-table rather than redefining it (stdlibtomllibaccepts it), so it now parses and round-trips instead of raisingRedefinition of an existing table. The concrete-table case ([a.b]then[a]b.z = 1) stays rejected. (#565)Eexponent after a leading-zero mantissa (e.g.0E2) being rejected as an invalid number while0e2parsed fine. (#586)Inf,NaN,-INF) being accepted; TOML only allows lowercaseinfandnan, so they now raiseParseError. (#628)item()reordering the keys of an inline table (dict-valued keys were forced last) under the defaultsort_keys=False. (#546)unwrap()moving a key to the end after its value was replaced (e.g.doc["b"] = 9), whiledumps()andkeys()kept the original order. (#591)", "separators emitting a bare","for the new entry, leaving the table inconsistently spaced (e.g.{x = 1, y = 2,z = 3}). (#595)key = [], placed and keyed relative to the nearest table header so it parses back into the same table. (#567)add_line(value, comment=...)) rendering its closing]on the comment line, producing unparseable output. (#580)del array[start:stop:step]with a negative or omitted bound removing the wrong elements from the rendered output. (#599)ValueError("slice assignment is not supported"). (#600)String.__add__splicing the appended text into a basic string without escaping it, so appending a quote or backslash produced invalid TOML. (#612)\rin a multiline basic string and rejected withInvalidStringErrorin a multiline literal string; CRLF line endings are left intact. (#539)datetime.timerendering with a UTC offset (e.g.07:32:00+02:00), which TOML local times do not allow; it now renders as a local time. (#613)+-0.0(e.g.-1.5times0), which does not parse. (#629)Boolitems never comparing equal to each other; they now compare by value. (#660)Configuration
📅 Schedule: (in timezone America/Toronto)
🚦 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 has been generated by Mend Renovate CLI.