Skip to content

chore(deps-dev): bump pytest from 8.3.4 to 9.0.3 in /src/kiro_crew/apps/builtins/aws_control/crew/runtime/container - #10665

Merged
iamwhatever merged 1 commit into
mainfrom
dependabot/pip/src/kiro_crew/apps/builtins/aws_control/crew/runtime/container/pytest-9.0.3
Oct 17, 2026
Merged

iamwhatever merged 1 commit into
mainfrom
dependabot/pip/src/kiro_crew/apps/builtins/aws_control/crew/runtime/container/pytest-9.0.3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 14, 2026

Copy link
Copy Markdown
Contributor

Bumps pytest from 8.3.4 to 9.0.3.

Release notes

Sourced from pytest's releases.

9.0.3

pytest 9.0.3 (2026-04-07)

Bug fixes

  • #12444: Fixed pytest.approx which now correctly takes into account ~collections.abc.Mapping keys order to compare them.

  • #13634: Blocking a conftest.py file using the -p no: option is now explicitly disallowed.

    Previously this resulted in an internal assertion failure during plugin loading.

    Pytest now raises a clear UsageError explaining that conftest files are not plugins and cannot be disabled via -p.

  • #13734: Fixed crash when a test raises an exceptiongroup with __tracebackhide__ = True.

  • #14195: Fixed an issue where non-string messages passed to unittest.TestCase.subTest() were not printed.

  • #14343: Fixed use of insecure temporary directory (CVE-2025-71176).

Improved documentation

  • #13388: Clarified documentation for -p vs PYTEST_PLUGINS plugin loading and fixed an incorrect -p example.
  • #13731: Clarified that capture fixtures (e.g. capsys and capfd) take precedence over the -s / --capture=no command-line options in Accessing captured output from a test function <accessing-captured-output>.
  • #14088: Clarified that the default pytest_collection hook sets session.items before it calls pytest_collection_finish, not after.
  • #14255: TOML integer log levels must be quoted: Updating reference documentation.

Contributor-facing changes

  • #12689: The test reports are now published to Codecov from GitHub Actions. The test statistics is visible on the web interface.

    -- by aleguy02

9.0.2

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 TERM is dumb, the escape codes are no longer emitted, even if the plugin is enabled.

  • #13904: Fixed the TOML type of the tmp_path_retention_count settings in the API reference from number to string.

  • #13946: The private config.inicfg attribute 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.

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [pytest](https://github.com/pytest-dev/pytest) from 8.3.4 to 9.0.3.
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@8.3.4...9.0.3)

---
updated-dependencies:
- dependency-name: pytest
  dependency-version: 9.0.3
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Sep 14, 2026
@dependabot
dependabot Bot requested review from a team and smeyffret September 14, 2026 02:05
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Sep 14, 2026
@NicholasRBowers NicholasRBowers added the needs-pr-triage PR scanner: awaiting automated triage label Sep 21, 2026
@NicholasRBowers

Copy link
Copy Markdown
Contributor

🤖 Kiro Crew [operator: NicholasRBowers#a942f9ca]: This PR has been inactive for 7+ days. I reviewed the blockers and they require a maintainer decision rather than branch work:

1. The only blocking check cannot be fixed from this branch. scan / internal-content-scan (job 103834777215) fails closed: the log shows ROLE: and BUCKET: interpolating empty, then the gate's deliberate exit 1 — "This run has no credentials for the ruleset, so the added lines were NOT scanned." GitHub withholds repository Actions secrets from dependabot-triggered pull_request runs (they live in a separate Dependabot secrets store), and internal-content-scan-gate.yml's if: skips only fork heads — this is a same-repo dependabot PR, so the job runs and fails by design. No commit, rebase or rerun makes the secrets appear. Precedent: @iamwhatever merged siblings #8179 (2026-09-18T21:37:38Z) and #6330 (21:34:40Z) with this same check still failing, so the class is resolved by ruleset Admin/Maintain bypass merge, or by adding KIRO_RELEASE_GATE_ROLE_ARN / KIRO_RELEASE_GATE_BUCKET to Settings → Secrets → Dependabot. Both are repo-config calls.

2. As written, this bump makes the file it edits uninstallable — and no check will ever catch it. requirements-dev.txt also pins pytest-asyncio==0.25.2, which declares pytest<9,>=8.2. Pinning pytest==9.0.3 beside it is unresolvable; verified by dry-run:

ERROR: Cannot install -r requirements-dev.txt (line 2) and pytest==9.0.3
because these package versions have conflicting dependencies.
The conflict is caused by:
    The user requested pytest==9.0.3
    pytest-asyncio 0.25.2 depends on pytest<9 and >=8.2
ERROR: ResolutionImpossible

The base pins (pytest==8.3.4) resolve cleanly. This is invisible to CI because nothing installs this file: ci.yml deliberately installs container/requirements.txt plus the repo's own dev group instead (see its comment at ci.yml:1680-1687), and Dockerfile:211 installs only container/requirements.txt. That is why all 84 other checks — including all five AI lanes — are green. The pin is consumed by a developer installing the container suite locally.

The decision needed: which exit do you want?

  • pytest-asyncio==1.3.0 or 1.4.0 — the only releases that permit pytest 9 (pytest<10,>=8.2 and >=8.4). But 0.x → 1.x is a breaking major that removed the event_loop fixture and changed loop-scope defaults, and seven container_tests/ files are asyncio tests. The repo's own dev group deliberately sits at pytest-asyncio==0.20.3 (pyproject.toml:34) for that reason, so this likely needs code changes too.
  • pytest-asyncio==0.20.3, matching the dev group — resolves with pytest 9, and would make this file share one resolution with the rootdir toolchain, which is exactly the contradiction ci.yml:1684-1687 documents today ("Its pytest==8.3.4 also contradicts the dev group's 9.0.3 … so the two sets cannot share one resolution"). But it is a downgrade.
  • Close, or keep 8.3.4 — ci.yml already treats this file as a separate resolution and never installs it, so the contradiction is tolerated by design.

Either way this cannot ride in a dependabot-managed PR: dependabot bumps one dependency per PR, and its own description notes that altering the branch stops it from managing the PR. Whichever pin you want for pytest-asyncio needs a maintainer commit or a hand-authored PR.

Everything else is clean: MERGEABLE, 1 commit, no conflict, GPT 5.6 / Opus 4.8 / Design / First Principles / UX all pass, 0 unresolved threads, 0 human reviews. (Three macOS shards are pending from a readiness self-heal; the same shards already passed in the original run.)

When this is ruled on, the pipeline will re-assess on its next cycle.

@NicholasRBowers NicholasRBowers added needs-author-decision PR blocked on author input and removed needs-pr-triage PR scanner: awaiting automated triage labels Sep 21, 2026
@iamwhatever
iamwhatever merged commit 36b1f19 into main Oct 17, 2026
104 of 124 checks passed
@iamwhatever
iamwhatever deleted the dependabot/pip/src/kiro_crew/apps/builtins/aws_control/crew/runtime/container/pytest-9.0.3 branch October 17, 2026 06:51
@github-actions github-actions Bot removed the readiness: action required A blocking check or review needs attention label Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file needs-author-decision PR blocked on author input python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants