Skip to content

build(deps): bump the python group across 1 directory with 21 updates - #425

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/python-8c37b4132d
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/python-8c37b4132d

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the python group with 21 updates in the / directory:

Package From To
agent-manifest 0.12.0 0.15.0
agentrust-trace 0.10.0 0.11.0
cmcp-runtime 0.7.0 0.7.1
openai 3.24.0 3.49.0
chap-coordinator 0.2.13 0.3.5
click 8.5.0 8.5.1
pydantic 2.13.5 2.14.3
pytest 9.1.1 9.2.0
certifi 2026.10.19 2026.10.23
openai-agents 0.22.3 0.24.0
uvicorn 0.52.4 0.54.0
langchain-core 1.6.3 1.8.0
langgraph 1.2.12 1.2.20
pypi-attestations 0.0.30 0.0.31
ruff 0.16.9 0.17.4
google-adk 2.11.0 2.14.0
python-dotenv 1.2.3 1.2.4
agent-passport-system 4.2.0 4.3.0
pydantic-ai-slim 2.53.0 2.67.0
numpy 2.5.3 2.5.4
pandas 3.0.6 3.1.1

Updates agent-manifest from 0.12.0 to 0.15.0

Release notes

Sourced from agent-manifest's releases.

python-v0.15.0

What's Changed

Full Changelog: agentrust-io/agent-manifest@python-v0.14.0...python-v0.15.0

python-v0.14.0

What's Changed

Full Changelog: agentrust-io/agent-manifest@python-v0.13.1...python-v0.14.0

python-v0.13.1

agent-manifest 0.13.1

pip install agent-manifest==0.13.1

Behaviour change

verify_evidence_pack() now reads the verdict inside the pack. A pack whose embedded section 5.2 verification_result says REVOKED, EXPIRED, MISMATCH or anything other than VALID returns FAILED. Under 0.13.0 the same pack returned VERIFIED. If you accepted those packs, they will now be rejected.

Fixed

  • [SDK] verify_evidence_pack() only checked that the embedded verification_result carried a known enum value, and never read its verification_signature. Now a non-VALID result fails the pack, a manifest_id that differs from the pack's manifest fails it, and a result with no manifest_id is MALFORMED. New keyword arguments result_key_id and result_algorithm check verification_signature over the new verification_result_pre_image(). Leave out result_key_id and the result reports verification_result_signature_verified=False with a verification_result_signature_not_appraised warning. signature_verified still covers the outer pack_signature only. (#463)
  • [SDK] verify_evidence_pack() and verify_trace_envelope() raised TypeError or ValueError on some untrusted input: a non-string verification_result.result or pack_signature.key_id, or a value RFC 8785 cannot represent (NaN, Infinity, a lone surrogate, an integer beyond 2^53, nesting deeper than 64). They now return MALFORMED. (#463)

Changed

  • [CI] CodeQL runs on every pull request and every push to main, with the python/** path filter and the Dependabot skip removed (#463). Write permissions in codeql.yml and docs.yml moved from workflow level to the job that needs them (#464). New ClusterFuzzLite target fuzz_trace.py covers both verifiers (#463).

Full changelog: agentrust-io/agent-manifest@python-v0.13.0...python-v0.13.1

agent-manifest 0.13.0 is on PyPI: pip install agent-manifest==0.13.0.

Compatibility: canonicalize() now follows RFC 8785 exactly (#404, closes #322). It no longer NFC-normalizes strings, no longer escapes U+2028, U+2029 or U+007F to U+009F, and refuses integers above 2**53 - 1. A signature that 0.12.0 made over a document containing any of those will not verify. Every other document canonicalizes to the same bytes as before.

Security fixes

  • #404: two distinct strings could share one signature, and two keys that normalized alike produced invalid JSON that silently dropped a signed field.
  • #450: verify_revocation_signature() compares signer_key_id in constant time.

... (truncated)

Changelog

Sourced from agent-manifest's changelog.

[0.15.0] - 2026-09-30

Security

  • [SDK] verify_attestation_chain() refuses debug guests. The SEV-SNP path never read the signed guest policy and the TDX path never parsed TDATTRIBUTES, so a debug-enabled guest with an allow-listed measurement returned passed=True. A debug guest's memory is readable and writable by the host, so its REPORT_DATA and the code that chose it are the host's to set. The verdict now fails when SNP guest policy DEBUG (bit 19, AMD 56860) or TDX TDATTRIBUTES.DEBUG (bit 0, TD report body offset 120) is set, read from the signed bytes after the signature verifies. SNP reports must also carry VMPL 0, the level both of this package's SNP producers request at (SEVSNPProvider through configfs-TSM, and the Azure paravisor). verify_runtime_report() and verify_runtime_freshness() apply the same checks with no opt-in. ChainVerificationResult gains debug and vmpl, read from the signed report (None without a verified signature, and for platforms with no such field). verify_attestation_chain(allow_debug=True) accepts a debug guest for development and records it in reasons; it does not relax VMPL. SnpReport.debug, TdxQuote.td_attributes and TdxQuote.debug expose the parsed state. Behaviour change: a debug guest, or an SNP report at VMPL 1 to 3, that previously verified now fails.

Added

  • [SDK] Experimental, opt-in evidence-requirements-experimental-v1 profile. A v0.2 manifest that declares it may carry a signed evidence_requirements block (components, required relationships, combination policy reference), and agent_manifest.evidence_requirements.verify_evidence_manifest() returns it only after verify_manifest() is VALID. Without the profile the block is still rejected as an unknown field, so existing manifests verify as before. Under the profile every 0.14.0 check still applies, including the signed audit_key_sealed rule under enforce_attestation. Not part of the specification; see docs/evidence-requirements-experimental.md. Consumer: agentrust-io/trace-spec#439.

Fixed

  • [SDK] attach_receipt() corrupted or crashed when the envelope's receipts header (label 394) wasn't already an array - a map became its keys, a string its characters, and null/0/false/"" were silently replaced with []. attach_approvals() was already fixed for the same issue in 0.13.0; attach_receipt() now works the same way: a non-array existing value raises CoseStructureError instead of being coerced or overwritten, and receipt itself must be bytes or bytearray. To replace the array, use attach_unprotected(envelope, HDR_RECEIPTS, receipts). Behaviour change: a bad receipt, or a non-array receipts value, now raises instead of being silently coerced.

... (truncated)

Commits
  • 2f1b9f5 fix(attestation): refuse debug guests and non-VMPL0 SNP reports, release 0.15...
  • 7466b3d feat(sdk): add opt-in experimental evidence-requirements profile (#479)
  • 7a28a4b docs(changelog): file the attach_receipt fix under Unreleased (#478)
  • d3ed22e fix attach receipt (#469)
  • 3c3f5a5 fix(attestation): read verdicts from signed evidence, pin the AMD root (0.14....
  • d991472 bump-urllib3-2.8.0 (#475)
  • 025247a docs(spec): correct identity framing, container-digest binding and Blackwell ...
  • 539c24c docs(spec): publish the two-tool catalog_hash vector in Appendix D (#470)
  • 2f54af9 chore(deps): bump the codeql-action group with 4 updates (#467)
  • 3c12491 docs(api): mark signing_pre_image() as v0.1-only (#460)
  • Additional commits viewable in compare view

Updates agentrust-trace from 0.10.0 to 0.11.0

Release notes

Sourced from agentrust-trace's releases.

agentrust-trace 0.11.0

Breaking

  • TraceAGTAdapter and TraceSandboxAdapter require enforcement_mode. They used to default to enforce, which signed a claim that a policy was evaluated when nothing evaluated it. Callers pass the mode their runtime ran under, or declared when no engine evaluated the policy (#416, #419; diagnosis and first fix by @​solloek369-arch in #417).
  • Signatures accept only canonical unpadded base64url, so one signature has one spelling. A padded or non-canonical signature that used to decode is refused (#418).

Added

  • verify_record() reports whether the objects a record cites resolve (#374).
  • Verifiers declare accepted_profiles, and VerificationResult records the profile it verified under (#347, for #116).
  • The reproducibility claim and its re-execution appraisal in the schema and models, with 21 signed vectors (#364, #370).
  • condition-appraisal is a registered references relation (#389).
  • MCP Server Provenance v2 binds behavioral hints (#409).
  • intent_bridge binds a successor observation by digest (#340).
  • provenance.verify_record() takes now to replay a freshness decision (#411).

Fixed

  • Schema patterns follow ECMA-262, so a trailing \n, \r, U+2028 or U+2029 no longer passes subject or URI checks (#388). The Pydantic models share the same patterns (#412).
  • A malformed signature is reported as malformed, not missing (#390).
  • Revocation bundles with no RFC 8785 form are unverified_for_revocation rather than an exception (#386).
  • Non-ASCII challenge nonces raise the documented ValueError (#383).
  • The AGT adapter no longer stamps appraisal.status: affirming on every record (#336), and both adapters check iat before signing (#343).
  • The v0.3 draft schema refused neither a private cnf.jwk nor an RSA key with no key material (#372, #311).
  • Input validation across content_marking, provenance, intent_bridge, revocation, the sandbox adapter and sign.verify_record() freshness bounds (#239, #282, #284, #287, #288, #290, #300, #305, #318, #322, #333, #334, #335, #339, #387, #410).
  • The PyPI description named TrustRecord.sign(), record.anchor() and record.verify(), none of which exist. It now shows sign_record and verify_record (#309).

Full list in CHANGELOG.md.

Changelog

Sourced from agentrust-trace's changelog.

[0.11.0] - 2026-09-25

  • Breaking: TraceSandboxAdapter and TraceAGTAdapter require enforcement_mode; it no longer defaults to "enforce". An evidence constructor that fills in "enforce" signs a claim that a policy was evaluated when nothing observed an evaluation (#416), and the first fix, a "declared" default (#417), is ruled out by spec section 4.3: declared MUST NOT be a default. Callers that omitted the argument now get a TypeError and must pass the mode their runtime actually ran under, or "declared" when no policy engine evaluated the policy. Runtime enforcement defaults are unchanged. Diagnosis and first fix by @​solloek369-arch.

  • Signatures accept one spelling. sign._b64url_decode accepts only canonical unpadded base64url, so a Trust Record, JWK x, provenance, intent-bridge or revocation-bundle signature carrying padding or non-canonical trailing bits is refused instead of decoding to the same bytes. content_marking refuses served record bytes with duplicate members. Deeply nested cnf.jwk, tool calls and provenance records raise each module's documented error type instead of RecursionError, and tool_catalog_hash raises ProvenanceError for a catalog with no anchor form. ClusterFuzzLite now covers the record, bundle, provenance, bridge, content-marking and canonicalization paths (#418).

  • Correct regulatory context in the published v0.1/v0.2 introductions and LIMITATIONS.md (#328, following #314). Separate Article 12 logging capability from TRACE tamper-evidence, identify Article 11 / Annex IV as documentation context, correct the applicability dates and remove unsupported TRACE-level compliance claims. Editorial only; reported by @​ioanavalea with review context from @​lywinged.

  • Propose v0.3 MCP profile requirements for producer-defined attempts, signed full declaration snapshots and explicit retry outcomes (#324). Clarify existing session wording without changing v0.2 validation. Proposed by @​madeinplutofabio with declaration-binding refinements from @​Mayur021; maintainer-carried proposal, not adopted or implemented.

  • Propose MCP Server Provenance v2 with normalized behavioral-hint binding (#406). Preserve v1 hashes and producer defaults; add explicit v2 production and consumer format requirements. Reported by @​altrudev.

  • Compare challenge nonces as UTF-8 bytes so non-ASCII mismatches raise the documented ValueError instead of TypeError (#381). Matching strings remain accepted without Unicode normalization. Invalid non-string expected_nonce settings raise a clear ValueError. Reported by @​chernistry; follow-up review by @​lywinged.

  • Report revocation bundles without an RFC 8785 form as unverified_for_revocation with cause bundle_malformed, while continuing record verification (#382). The direct bundle-digest API still refuses such input. Reported by @​chernistry.

  • Regenerate the v0.3 draft after canonical reproducibility additions and make the schema inventory test use portable repository paths on Windows.

  • Keep untrusted input on each verifier's documented error type. Nesting a few hundred levels deep in cnf.jwk, a tool call, a provenance record or served content-marking bytes raised RecursionError; a 4,400 digit URL port raised Python's integer-string ValueError; a float or unsafe integer in an offered tool's input_schema raised UnanchorableValue from check_tool_catalog. All were refusals already, none was an acceptance. Found by the new ClusterFuzzLite targets in .clusterfuzzlite/; regression tests in tests/test_untrusted_input_stays_on_the_documented_error.py.

  • Decode signatures and JWK x as canonical unpadded base64url only. The decoder took the standard alphabet, = padding and stray characters, and ignored the unused bits of the last character, so one signature had several spellings that all verified, and a revocation bundle's bundle_digest (which covers sig.value) gave one bundle several identities. The record-level rule

... (truncated)

Commits
  • 7d8df34 chore(release): agentrust-trace 0.11.0 (#420)
  • 3d7c90f fix(adapters): require enforcement_mode in the AGT and sandbox adapters (supe...
  • 5d9cf72 fix(security): strict signature decoding, documented refusals, ClusterFuzzLit...
  • 9fd79b6 fix(provenance): allow an explicit verification instant (#411)
  • 761783a docs(spec): name the instrument that set the Chapter III application dates (#...
  • e3111c7 docs: separate regulatory logging duties from TRACE properties (#414)
  • 9d303c5 docs: propose stateless MCP transcript profile requirements (#413)
  • b217e60 fix(validation): share schema regex semantics across Python surfaces (#412)
  • 0cbb72c fix(content-marking): require a textual profile identifier (#410)
  • 7d3f8ac feat(provenance): bind behavioral hints in explicit v2 format (#409)
  • Additional commits viewable in compare view

Updates cmcp-runtime from 0.7.0 to 0.7.1

Release notes

Sourced from cmcp-runtime's releases.

cmcp 0.7.1

Three security fixes, backported onto 0.7.0 so they ship without the breaking Agent Manifest binding change and the opaque provider removal waiting on main. Full detail in CHANGELOG.

  • GHSA-frxc-7f57-6f4r: deny a Cedar Allow that comes with evaluation errors, instead of skipping the errored policy and allowing.
  • GHSA-mrcx-xvv4-m7f8: bound the TPM AIA certificate fetch. Each hop resolves the host once, connects only to that checked address, and the hop and byte limits hold.
  • GHSA-2p85-666x-xm7x: classify upstream drift against the drifted tool's own catalog entry.

SDK on PyPI as cmcp-runtime 0.7.1.

Changelog

Sourced from cmcp-runtime's changelog.

[0.7.1] - 2026-10-19

Security

  • A Cedar Allow reached with evaluation errors was enforced as Allow (GHSA-frxc-7f57-6f4r). Cedar skips a policy whose condition errors, so a forbid reading a context attribute the current phase does not carry could not stop a matching permit. CedarBackend now denies any Allow that comes with evaluation errors, and the error reaches the tool_call or egress_denied audit row. So that a policy written for one phase does not deny in the other, both phases now carry the same context keys: egress adds session_max_sensitivity (the label string), arguments, baa_covered, compliance_domain, server_identity, destination_class and attestation_platform, and ingress adds egress (false), sensitivity_level, injection_events, reset_count and response_size_bytes (0). Without this the shipped BFSi demo denied every response at egress. A policy that reads a key outside that set, or workflow_id when the caller declared none, now denies.
  • The TPM AIA certificate fetch was unbounded (GHSA-mrcx-xvv4-m7f8). The chain walk followed redirects to any address and read responses without a limit. It now refuses destinations that do not resolve to global addresses, checks every redirect the same way, follows at most three and ignores responses over 64 KiB. Each hop's host is resolved once and the connection goes to the checked address (the request still names the host, and HTTPS still verifies the certificate against it), so a second DNS answer cannot point the fetch somewhere else. The fetch no longer uses environment proxies. An on-prem CA whose AIA host has a private address falls back to the vendored bundle.
  • Upstream drift was classified against the wrong catalog entry (GHSA-2p85-666x-xm7x). The scanner received the server of whichever entry was last in the catalog. Detection and fail-closed denial were not affected; only the classification written to the audit row was.
Commits
  • 4a7163a fix(security): cmcp-runtime 0.7.1 backport (Cedar errors, AIA fetch, drift cl...
  • See full diff in compare view

Updates openai from 3.24.0 to 3.49.0

Release notes

Sourced from openai's releases.

v3.49.0

3.49.0 (2026-11-10)

Features

Bug Fixes

  • encode microphone recordings as valid PCM WAV (#3900) (13c000d)

v3.48.0

3.48.0 (2026-11-09)

Features

  • api: add stream options for agent sessions (#4251) (c6fc264)
  • api: recognize gpt-6-rosalind in beta Responses (#4257) (3774b7e)

Chores

  • api: retain agent scheduling support (#4255) (a1175a3)
  • deps: bump locked multidict from 6.9.1 to 7.1.0 (#4259) (28cdb1b)
  • deps-dev: bump the python-maintenance group with 5 updates (#4258) (4b10e22)
  • deps-dev: bump types-requests from 2.33.0.20261006 to 2.33.0.20261030 (#4260) (de498d7)

Documentation

v3.47.0

3.47.0 (2026-11-05)

Features

v3.46.0

3.46.0 (2026-11-05)

Features

  • api: add Australia, India, and Japan residency options (#4246) (2634b87)

... (truncated)

Changelog

Sourced from openai's changelog.

3.49.0 (2026-11-10)

Features

Bug Fixes

  • encode microphone recordings as valid PCM WAV (#3900) (13c000d)

3.48.0 (2026-11-09)

Features

  • api: add stream options for agent sessions (#4251) (c6fc264)
  • api: recognize gpt-6-rosalind in beta Responses (#4257) (3774b7e)

Chores

  • api: retain agent scheduling support (#4255) (a1175a3)
  • deps: bump locked multidict from 6.9.1 to 7.1.0 (#4259) (28cdb1b)
  • deps-dev: bump the python-maintenance group with 5 updates (#4258) (4b10e22)
  • deps-dev: bump types-requests from 2.33.0.20261006 to 2.33.0.20261030 (#4260) (de498d7)

Documentation

3.47.0 (2026-11-05)

Features

3.46.0 (2026-11-05)

Features

  • api: add Australia, India, and Japan residency options (#4246) (2634b87)
  • api: add GPT-6 Rosalind to the model catalog (#4243) (0f8e5f3)
  • api: add image complexity and GIF and SVG output controls (#4247) (0152e3a)
  • api: expand agent turn errors and image and audio options (#4245) (1b2fb74)

... (truncated)

Commits
  • 3d573c0 release: 3.49.0 (#4263)
  • ea07983 feat(api): add typed async function tools (#4264)
  • 13c000d fix: encode microphone recordings as valid PCM WAV (#3900)
  • 7e1582c release: 3.48.0 (#4252)
  • de498d7 chore(deps-dev): bump types-requests from 2.33.0.20261006 to 2.33.0.20261030 ...
  • 28cdb1b chore(deps): bump multidict from 6.9.1 to 7.1.0 (#4259)
  • 4b10e22 chore(deps-dev): bump the python-maintenance group with 5 updates (#4258)
  • 3774b7e feat(api): recognize gpt-6-rosalind in beta Responses (#4257)
  • a1175a3 chore(api): retain agent scheduling support (#4255)
  • 44b1555 docs: consolidate AGENTS.md guidance (#4254)
  • Additional commits viewable in compare view

Updates chap-coordinator from 0.2.13 to 0.3.5

Release notes

Sourced from chap-coordinator's releases.

CHAP 0.3.5: who decides, who joins, and CHAP you can run

The protocol packages move together to 0.3.5, and two packages join them: @brightbeamai/chap-server, the desk server, and @brightbeamai/chap-code-gate, the code gate, both taken out of the generated projects so an upgrade reaches them. chap-analytics 0.2.6, on its own track, reads what 0.3.5 records.

Most of the coordinator changes close ways a review could be settled by someone other than an independent person, or a member could join under a name or a role nobody gave it. They change what the specification requires, which would make a minor release; as security fixes they ship as a patch release on the supported 0.3 line, as SECURITY.md sets out and as 0.3.4 did. Many refuse calls 0.3.4 accepted: "Upgrading" below lists each one and what to send in its place.

npm install @brightbeamai/chap-coordinator@0.3.5
pip install "chap-coordinator[crypto]==0.3.5" "chap-analytics==0.2.6"
npx create-chap-app@0.3.5 upgrade my-project

The security advisories give the details of each security fix, and CHANGELOG.md has this entry in full.

Security

  • A review a task requires is opened by its work, and decided by people. On a task that requires review, the review opens only on task.complete, from the assignee, under the workspace's review_rule; review.request only adds people to a review already open, and before it opens is refused with -32011, whoever sends it. Only type: "human" members decide it, and a reviewer set the coordinator picks holds only people.
  • The authors of the work do not decide its review. The assignee and the member that completed the work are recorded as the review's authors, and a decide.*, abstain.declare or review.acknowledge from one of them is refused with -32011, however the review is addressed. The authors go with the work: a new round keeps the earlier rounds' authors, a task escalate.raise or control.supersede makes carries the authors of the task it replaces as prior_authors, and a task task.route or handoff.accept moves keeps there the member it leaves, where that member moved it on itself. A member another member passed the task to stays a reviewer, so nobody can leave a person out of a review by routing the work through them. A reviewer's decision that completed a task, or a route of a completed task, is not taken for a completion of the work.
  • Its authors do not end a review. Only an author takes the work back to revise it; a task under review is not declined before a reviewer

... (truncated)

Changelog

Sourced from chap-coordinator's changelog.

0.3.5: who decides, who joins, and CHAP you can run

The protocol packages move together to 0.3.5, and two packages join them: @brightbeamai/chap-server, the desk server, and @brightbeamai/chap-code-gate, the code gate, both taken out of the generated projects so an upgrade reaches them. chap-analytics 0.2.6, on its own track, reads what 0.3.5 records.

Most of the coordinator changes close ways a review could be settled by someone other than an independent person, or a member could join under a name or a role nobody gave it. They change what the specification requires, which would make a minor release; as security fixes they ship as a patch release on the supported 0.3 line, as SECURITY.md sets out and as 0.3.4 did. Many refuse calls 0.3.4 accepted: "Upgrading" below lists each one and what to send in its place.

Security

  • A review a task requires is opened by its work, and decided by people. On a task that requires review, the review opens only on task.complete, from the assignee, under the workspace's review_rule; review.request only adds people to a review already open, and before it opens is refused with -32011, whoever sends it. Only type: "human" members decide it, and a reviewer set the coordinator picks holds only people.
  • The authors of the work do not decide its review. The assignee and the member that completed the work are recorded as the review's authors, and a decide.*, abstain.declare or review.acknowledge from one of them is refused with -32011, however the review is addressed. The authors go with the work: a new round keeps the earlier rounds' authors, a task escalate.raise or control.supersede makes carries the authors of the task it replaces as prior_authors, and a task task.route or handoff.accept moves keeps there the member it leaves, where that member moved it on itself. A member another member passed the task to stays a reviewer, so nobody can leave a person out of a review by routing the work through them. A reviewer's decision that completed a task, or a route of a completed task, is not taken for a completion of the work.
  • Its authors do not end a review. Only an author takes the work back to revise it; a task under review is not declined before a reviewer rejects it; escalate.raise hands the review on with the work; and from the moment a required review opens until a reviewer rejects the round, its authors cannot end the task with control.cancel, control.supersede, or a pause and then task.update to cancelled, under review or after taking the work back, nor end a successor an escalation or a supersede makes, which nobody declines either. A task that has held a review completes only through a decision: completing it again opens a new round.
  • A workspace sets its review rule. workspace.create takes review_rule (any_one_approves, all_approve or quorum:<n>), so a

... (truncated)

Commits
  • f7dfe94 Tests: compare temporary paths by their real path, as on macOS
  • f7283e0 Templates: the generator's tests run on the workspace's packages built
  • 8d36d96 CI on Node 24: the A2A reference server says when it listens, and the generat...
  • 1001581 CI: no bare require in TypeScript sources, and the bridges' framework tests t...
  • 4621211 chap-server README: what a quiet server prints about the enrolment code
  • 1f8329c The fourth review's fixes: chains of any length, decided reviews, and stores ...
  • d50e9e6 The third review's fixes: successors hold a review's authors, and authors are...
  • ef201d3 Conformance harness: the lockfile names Node 22 as its package does
  • 5374124 Bridge tests: the person's first join takes the desk server's enrolment code
  • d98623d Servers, code gate and upgrade: the second review's fixes
  • Additional commits viewable in compare view

Updates click from 8.5.0 to 8.5.1

Release notes

Sourced from click's releases.

8.5.1

This is the Click 8.5.1 fix release, which fixes bugs but does not otherwise change behavior and should not result in breaking changes compared to the latest feature release.

PyPI: https://pypi.org/project/click/8.5.1/ Changes: https://click.palletsprojects.com/page/changes/#version-8-5-1 Milestone: https://github.com/pallets/click/milestone/66

  • Fix copy.deepcopy() and pickle on a Parameter, Option or Command. #3805
  • A KeyboardInterrupt arriving while Command.main() reports an abort or an error, or while it exits, no longer escapes as an unhandled traceback. The command still exits with the intended code; only the message may be lost. #3802
  • Add Option.get_help_spec(), which returns the option's left help column even when the option is hidden. Option.get_help_record() still returns None for hidden options, so help screens are unchanged. #3821
  • The Positional arguments help section lists every argument of the command, not only the documented ones. An argument with no help gets an empty description, the same way an option with no help does. #3860
  • Argument.get_help_record() always returns a tuple. It used to return None for an argument with no help. #3860
  • Document which types are inferred from default, and what an unrecognized type callable does to a command-line value. #3036 #3808
  • path_type narrows the converted value's type for convert and prompt. #3822 #3858
  • Parameter accepts a new help argument, and Option and Argument inherit it. Parameter.to_info_dict() now reports help for every kind of parameter. #3861
  • A command's short help no longer stops at an abbreviation such as vs. or e.g. inside the first sentence. A period ends the sentence only when it closes the text or the next word does not start in lowercase. #3865
  • With show_envvar=True, an option's error message now prints all variables of an envvar sequence instead of the repr of the sequence. #3884
  • An empty envvar, such as [] or "", shows the same help and error message as no envvar when show_envvar=True. The help screen used to show [env var: ]. #3884
  • Align command's deprecated help text to options and arguments: do not translate the command's own help text, only the (DEPRECATED) label. #3901
Changelog

Sourced from click's changelog.

Version 8.5.1

Released 2026-11-09

  • Fix copy.deepcopy() and pickle on a Parameter, Option or Command. {pr}3805
  • A KeyboardInterrupt arriving while Command.main() reports an abort or an error, or while it exits, no longer escapes as an unhandled traceback. The command still exits with the intended code; only the message may be lost. {issue}3802
  • Add {meth}Option.get_help_spec, which returns the option's left help column even when the option is hidden. {meth}Option.get_help_record still returns None for hidden options, so help screens are unchanged. {pr}3821
  • The Positional arguments help section lists every argument of the command, not only the documented ones. An argument with no help gets an empty description, the same way an option with no help does. {pr}3860
  • {meth}Argument.get_help_record always returns a tuple. It used to return None for an argument with no help. {pr}3860
  • Document which types are inferred from default, and what an unrecognized type callable does to a command-line value. {issue}3036 {pr}3808
  • path_type narrows the converted value's type for convert and prompt. {issue}3822 {pr}3858
  • {class}Parameter accepts a new help argument and {class}Option and {class}Argument inherits it. {meth}Parameter.to_info_dict now reports help for every kind of parameter. {pr}3861
  • A command's short help no longer stops at an abbreviation such as vs. or e.g. inside the first sentence. A period ends the sentence only when it closes the text or the next word does not start in lowercase. {pr}3865
  • With show_envvar=True, an option's error message now prints all variables of an envvar sequence instead of the repr of the sequence. {pr}3884
  • An empty envvar, such as [] or "", shows the same help and error message as no envvar when show_envvar=True. The help screen used to show [env var: ]. {pr}3884
  • Align command's deprecated help text to options and arguments: do not translate the command's own help text, only the (DEPRECATED) label. {pr}3901
Commits
  • cf19179 Release version 8.5.1
  • 1ff766d Remove documentation changelog entry.
  • 16da191 Add a standalone application guide for Nuitka (#3897)
  • 473f652 Remove issue and PR references outside the changelog (#3905)
  • df7fe0b Remove issue and PR references outside the changelog
  • 4fd4206 Bump pypa/gh-action-pypi-publish to v1.14.3 (#3906)
  • 9048ab0 Bump pypa/gh-action-pypi-publish to v1.14.3
  • ff0c369 Add a standalone application guide for Nuitka
  • 5125851 Stop passing a deprecated command's help text through gettext (#3901)
  • 6d34602 Additional round-trip tests for unstyle() (#3899)
  • Additional commits viewable in compare view

Updates pydantic from 2.13.5 to 2.14.3

Release notes

Sourced from pydantic's releases.

v2.14.3 2026-11-04

v2.14.3 (2026-11-04)

What's Changed

Packaging

  • Build wheels for GraalPy 3.13 by @​msimacek in #14136.

    The previous v2.14.2 release published GraalPy 3.11 wheels, which were no...

    Description has been truncated

Bumps the python group with 21 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [agent-manifest](https://github.com/agentrust-io/agent-manifest) | `0.12.0` | `0.15.0` |
| [agentrust-trace](https://github.com/agentrust-io/trace-spec) | `0.10.0` | `0.11.0` |
| [cmcp-runtime](https://github.com/agentrust-io/cmcp) | `0.7.0` | `0.7.1` |
| [openai](https://github.com/openai/openai-python) | `3.24.0` | `3.49.0` |
| [chap-coordinator](https://github.com/BrightbeamAI/chap) | `0.2.13` | `0.3.5` |
| [click](https://github.com/pallets/click) | `8.5.0` | `8.5.1` |
| [pydantic](https://github.com/pydantic/pydantic) | `2.13.5` | `2.14.3` |
| [pytest](https://github.com/pytest-dev/pytest) | `9.1.1` | `9.2.0` |
| [certifi](https://github.com/certifi/python-certifi) | `2026.10.19` | `2026.10.23` |
| [openai-agents](https://github.com/openai/openai-agents-python) | `0.22.3` | `0.24.0` |
| [uvicorn](https://github.com/Kludex/uvicorn) | `0.52.4` | `0.54.0` |
| [langchain-core](https://github.com/langchain-ai/langchain) | `1.6.3` | `1.8.0` |
| [langgraph](https://github.com/langchain-ai/langgraph) | `1.2.12` | `1.2.20` |
| [pypi-attestations](https://github.com/pypi/pypi-attestations) | `0.0.30` | `0.0.31` |
| [ruff](https://github.com/astral-sh/ruff) | `0.16.9` | `0.17.4` |
| [google-adk](https://github.com/google/adk-python) | `2.11.0` | `2.14.0` |
| [python-dotenv](https://github.com/theskumar/python-dotenv) | `1.2.3` | `1.2.4` |
| [agent-passport-system](https://github.com/agent-passport-system/agent-passport-python) | `4.2.0` | `4.3.0` |
| [pydantic-ai-slim](https://github.com/pydantic/pydantic-ai) | `2.53.0` | `2.67.0` |
| [numpy](https://github.com/numpy/numpy) | `2.5.3` | `2.5.4` |
| [pandas](https://github.com/pandas-dev/pandas) | `3.0.6` | `3.1.1` |



Updates `agent-manifest` from 0.12.0 to 0.15.0
- [Release notes](https://github.com/agentrust-io/agent-manifest/releases)
- [Changelog](https://github.com/agentrust-io/agent-manifest/blob/main/CHANGELOG.md)
- [Commits](agentrust-io/agent-manifest@python-v0.12.0...python-v0.15.0)

Updates `agentrust-trace` from 0.10.0 to 0.11.0
- [Release notes](https://github.com/agentrust-io/trace-spec/releases)
- [Changelog](https://github.com/agentrust-io/trace-spec/blob/main/CHANGELOG.md)
- [Commits](agentrust-io/trace-spec@v0.10.0...v0.11.0)

Updates `cmcp-runtime` from 0.7.0 to 0.7.1
- [Release notes](https://github.com/agentrust-io/cmcp/releases)
- [Changelog](https://github.com/agentrust-io/cmcp/blob/main/CHANGELOG.md)
- [Commits](agentrust-io/cmcp@v0.7.0...v0.7.1)

Updates `openai` from 3.24.0 to 3.49.0
- [Release notes](https://github.com/openai/openai-python/releases)
- [Changelog](https://github.com/openai/openai-python/blob/main/CHANGELOG.md)
- [Commits](openai/openai-python@v3.24.0...v3.49.0)

Updates `chap-coordinator` from 0.2.13 to 0.3.5
- [Release notes](https://github.com/BrightbeamAI/chap/releases)
- [Changelog](https://github.com/BrightbeamAI/chap/blob/main/CHANGELOG.md)
- [Commits](BrightbeamAI/chap@v0.2.13...v0.3.5)

Updates `click` from 8.5.0 to 8.5.1
- [Release notes](https://github.com/pallets/click/releases)
- [Changelog](https://github.com/pallets/click/blob/main/CHANGES.md)
- [Commits](pallets/click@8.5.0...8.5.1)

Updates `pydantic` from 2.13.5 to 2.14.3
- [Release notes](https://github.com/pydantic/pydantic/releases)
- [Changelog](https://github.com/pydantic/pydantic/blob/main/HISTORY.md)
- [Commits](pydantic/pydantic@v2.13.5...v2.14.3)

Updates `pytest` from 9.1.1 to 9.2.0
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@9.1.1...9.2.0)

Updates `certifi` from 2026.10.19 to 2026.10.23
- [Commits](certifi/python-certifi@2026.10.19...2026.10.23)

Updates `openai-agents` from 0.22.3 to 0.24.0
- [Release notes](https://github.com/openai/openai-agents-python/releases)
- [Changelog](https://github.com/openai/openai-agents-python/blob/main/CHANGELOG.md)
- [Commits](openai/openai-agents-python@v0.22.3...v0.24.0)

Updates `uvicorn` from 0.52.4 to 0.54.0
- [Release notes](https://github.com/Kludex/uvicorn/releases)
- [Changelog](https://github.com/Kludex/uvicorn/blob/main/docs/release-notes.md)
- [Commits](Kludex/uvicorn@0.52.4...0.54.0)

Updates `langchain-core` from 1.6.3 to 1.8.0
- [Release notes](https://github.com/langchain-ai/langchain/releases)
- [Commits](langchain-ai/langchain@langchain-core==1.6.3...langchain-core==1.8.0)

Updates `langgraph` from 1.2.12 to 1.2.20
- [Release notes](https://github.com/langchain-ai/langgraph/releases)
- [Commits](langchain-ai/langgraph@1.2.12...1.2.20)

Updates `pypi-attestations` from 0.0.30 to 0.0.31
- [Release notes](https://github.com/pypi/pypi-attestations/releases)
- [Changelog](https://github.com/pypi/pypi-attestations/blob/main/CHANGELOG.md)
- [Commits](pypi/pypi-attestations@v0.0.30...v0.0.31)

Updates `ruff` from 0.16.9 to 0.17.4
- [Release notes](https://github.com/astral-sh/ruff/releases)
- [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md)
- [Commits](astral-sh/ruff@0.16.9...0.17.4)

Updates `google-adk` from 2.11.0 to 2.14.0
- [Release notes](https://github.com/google/adk-python/releases)
- [Changelog](https://github.com/google/adk-python/blob/main/CHANGELOG.md)
- [Commits](google/adk-python@v2.11.0...v2.14.0)

Updates `python-dotenv` from 1.2.3 to 1.2.4
- [Release notes](https://github.com/theskumar/python-dotenv/releases)
- [Changelog](https://github.com/theskumar/python-dotenv/blob/main/CHANGELOG.md)
- [Commits](theskumar/python-dotenv@v1.2.3...v1.2.4)

Updates `agent-passport-system` from 4.2.0 to 4.3.0
- [Release notes](https://github.com/agent-passport-system/agent-passport-python/releases)
- [Changelog](https://github.com/agent-passport-system/agent-passport-python/blob/main/CHANGELOG.md)
- [Commits](agent-passport-system/agent-passport-python@v4.2.0...v4.3.0)

Updates `pydantic-ai-slim` from 2.53.0 to 2.67.0
- [Release notes](https://github.com/pydantic/pydantic-ai/releases)
- [Changelog](https://github.com/pydantic/pydantic-ai/blob/main/docs/changelog.md)
- [Commits](pydantic/pydantic-ai@v2.53.0...v2.67.0)

Updates `numpy` from 2.5.3 to 2.5.4
- [Release notes](https://github.com/numpy/numpy/releases)
- [Changelog](https://github.com/numpy/numpy/blob/main/doc/RELEASE_WALKTHROUGH.rst)
- [Commits](numpy/numpy@v2.5.3...v2.5.4)

Updates `pandas` from 3.0.6 to 3.1.1
- [Release notes](https://github.com/pandas-dev/pandas/releases)
- [Commits](pandas-dev/pandas@v3.0.6...v3.1.1)

---
updated-dependencies:
- dependency-name: agent-manifest
  dependency-version: 0.15.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: agentrust-trace
  dependency-version: 0.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: cmcp-runtime
  dependency-version: 0.7.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python
- dependency-name: openai
  dependency-version: 3.49.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: chap-coordinator
  dependency-version: 0.3.5
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: click
  dependency-version: 8.5.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python
- dependency-name: pydantic
  dependency-version: 2.14.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: pytest
  dependency-version: 9.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: certifi
  dependency-version: 2026.10.23
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python
- dependency-name: openai-agents
  dependency-version: 0.24.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: uvicorn
  dependency-version: 0.54.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: langchain-core
  dependency-version: 1.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: langgraph
  dependency-version: 1.2.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python
- dependency-name: pypi-attestations
  dependency-version: 0.0.31
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python
- dependency-name: ruff
  dependency-version: 0.17.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: google-adk
  dependency-version: 2.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: python-dotenv
  dependency-version: 1.2.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python
- dependency-name: agent-passport-system
  dependency-version: 4.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: pydantic-ai-slim
  dependency-version: 2.67.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: numpy
  dependency-version: 2.5.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python
- dependency-name: pandas
  dependency-version: 3.1.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested review from a team, carloshvp and imran-siddique as code owners November 15, 2026 01:48
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Nov 15, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Nov 16, 2026
@dependabot
dependabot Bot deleted the dependabot/pip/python-8c37b4132d branch November 16, 2026 04:42
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 python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants