Repository navigation
chore(release): v2.7.1 — correctifs de sécurité du lock, CI 3.14, test corrigé - #289
Conversation
…t corrigé Release de maintenance, sans changement runtime : xcore/ et les bornes de dépendances de pyproject.toml sont identiques à la 2.7.0. - lock : 11 alertes Dependabot fermées (anyio, urllib3, virtualenv, mkdocs-material) — #286 - alerte CodeQL #29 rejetée comme faux positif (littéral d'énumération ExecutionMode.TRUSTED journalisé), sans changement de code - test : plus de RLIMIT_AS posé sur le process pytest (can't start new thread en 3.14) + garde-fou dans conftest — #288 - CI : matrice 3.12 / 3.13 / 3.14 — #288
There was a problem hiding this comment.
Sorry @traoreera, you've used your own review budget of 250,000 diff characters for the last 7 days.
You can request another review in 1 day and 10 hours by commenting @sourcery-ai review. Upgrade to get a review now.
Reviewer's GuideThis maintenance release only updates versioning and release documentation while incorporating already-merged repository changes: a targeted poetry.lock security refresh, protection against irreversible resource-limit mutations in tests, and Python 3.14 CI coverage. Runtime sources and dependency ranges remain unchanged from 2.7.0; reviewers should verify version consistency, lockfile integrity, the resource-limit isolation guard, and the CI matrix before tagging and publishing. Flow diagram for protected resource-limit testingflowchart LR
T[TestMemoryLimiter.test_apply_positive] --> P[resource.setrlimit patched]
P --> A[Assert MemoryLimiter.apply call]
F[autouse fixture] --> G[Guard RLIMIT_AS RLIMIT_DATA RLIMIT_CPU]
G --> X[Fail test if process limits change]
Flow diagram for the 2.7.1 release updateflowchart LR
V[Version sources] --> B[2.7.1]
C[Changelog documentation] --> B
B --> W[Build wheel]
W --> I[Install in clean virtualenv]
I --> Q[Verify import boot and plugin execution]
Q --> T[Tag and publish after merge]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Résumé
Release de maintenance 2.7.1, sans changement runtime :
xcore/et les bornes de dépendances depyproject.tomlsont identiques à la 2.7.0 (vérifié :git diff v2.7.0 main -- xcore pyproject.tomlest vide). Le wheel publié se comporte exactement comme la 2.7.0 ; cette version embarque le rafraîchissement de sécurité et les correctifs de test/CI déjà fusionnés dansmain.Contenu (déjà dans
main)anyio4.14.1 → 4.15.1,urllib32.7.0 → 2.8.0,virtualenv21.6.0 → 21.14.3,mkdocs-material9.7.6 → 9.7.7. Concerne le dev, la CI et les builds qui installent depuis le lock ;pip install XCoreRuntimerésout ses propres versions.from_rawmethod on plugin dependencecy #29 rejetée comme faux positif (littéral d'énumérationExecutionMode.TRUSTED = "trusted"journalisé), sans changement de code.test_apply_positiveposait réellementRLIMIT_AS=512 Mosur le process pytest (irréversible) →can't start new threaden 3.14. Corrigé + garde-fou danstests/conftest.py.Cette PR
Bump
2.7.0 → 2.7.1(pyproject.toml,xcore/__version__.py—__version__et__version_info__), entrée[2.7.1]dansCHANGELOG.mdetdoc/changelog.md,CLAUDE.md.Vérification
import xcore, boot zero-config, un plugin trusted et un plugin sandboxed appelés — OK.v2.7.1(donc la publication PyPI) ne sera posé qu'après la fusion.Summary by Sourcery
Release version 2.7.1 with refreshed locked dependencies, safer resource-limit testing, and Python 3.14 CI coverage.
Bug Fixes:
Enhancements:
Build:
Documentation:
Chores: