chore(deps): bump cryptography from 48.0.0 to 50.0.0 in /envs/calendar_env

[dependabot]

Bumps cryptography from 48.0.0 to 50.0.0.

Changelog

Sourced from cryptography's changelog.

50.0.0 - 2026-07-31

* **SECURITY ISSUE**:
  :func:`~cryptography.hazmat.primitives.serialization.pkcs7.pkcs7_decrypt_der`
  and its PEM and S/MIME variants no longer expose distinguishable errors or
  timing when unwrapping a ``RecipientInfo``'s ``encryptedKey``, which could
  act as a Bleichenbacher oracle for callers that decrypt untrusted messages.
  A random key is now substituted on failure, as described in :rfc:`3218`.
  Credit to **@X1AOxiang** for reporting the issue. **CVE-2026-69247**
* Deprecated Diffie-Hellman key exchange over finite fields (FFDH).
  Everything FFDH is deprecated, including the types in
  ``cryptography.hazmat.primitives.asymmetric.dh`` and loading FFDH keys or
  parameters with the key loading APIs. Users should migrate to a more
  modern key exchange algorithm.
* Added ``xof()`` class methods to
  :class:`~cryptography.hazmat.primitives.hashes.SHAKE128` and
  :class:`~cryptography.hazmat.primitives.hashes.SHAKE256` for constructing
  algorithm instances configured for use with
  :class:`~cryptography.hazmat.primitives.hashes.XOFHash`.
* The :mod:`X.509 verification <cryptography.x509.verification>` APIs are now
  considered stable and are subject to our API stability policy.
* Added the :doc:`/cobblestone` recipe, an implementation of the
  Cobblestone-128 and Cobblestone-256 instantiations of the `C2SP
  chunked-encryption specification
  <https://c2sp.org/chunked-encryption>`_ for streaming authenticated
  encryption of large messages.
* Parsing a Signed Certificate Timestamp list now rejects encodings that
  carry trailing bytes after the list or after an individual SCT, instead of
  silently ignoring them.
* Added support for using :class:`~cryptography.x509.Name` as a field type in
  the :doc:`/hazmat/asn1/index` module.
* Loading a public key or an EC private key now rejects DER where the
  ``subjectPublicKey`` (or EC ``publicKey``) ``BIT STRING`` declares a non-zero
  number of unused bits, instead of silently ignoring it.
* Parsing a CRL entry's ``InvalidityDate`` extension now rejects a
  ``GeneralizedTime`` that carries fractional seconds or another non-DER form,
  matching the strict encoding already required for every other X.509 time
  field.
* :func:`~cryptography.x509.ocsp.load_der_ocsp_request` and
  :func:`~cryptography.x509.ocsp.load_der_ocsp_response` now reject a request
  or response whose ``version`` field is not ``v1``, the only version defined
  by RFC 6960, matching the version validation already performed when loading
  certificates, CSRs and CRLs.
* :class:`~cryptography.hazmat.primitives.hashes.XOFHash` is now supported
  when building against AWS-LC.
* HMAC (and therefore PBKDF2-HMAC) with SHA-3 hashes is now supported when
  building against AWS-LC.
* Diffie-Hellman (:doc:`/hazmat/primitives/asymmetric/dh`) is now supported
  when building against AWS-LC.
</tr></table> 

... (truncated)

Commits

• dcb7050 Prepare for 50.0.0 release (#15372)
• 53fccd9 Don't leak how PKCS#7 encryptedKey decryption failed (#15369)
• d472f97 Add from __future__ import annotations to all src/ Python files (#15371)
• 908773d Bump downstream dependencies in CI (#15368)
• 2cc07cc Bump BoringSSL, OpenSSL, AWS-LC in CI (#15367)
• c94ede9 chore(deps): bump ruff from 0.16.0 to 0.16.1 (#15366)
• 67a8308 chore(deps): bump virtualenv from 21.7.0 to 21.7.1 (#15365)
• 95018ff Release the GIL in one-shot AEAD encrypt/decrypt (#15361)
• 6954733 Release the GIL during DH and DSA parameter generation (#15364)
• 6893b94 Import _serialization instead of serialization in x509/extensions (#15363)
• Additional commits viewable in compare view

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.

---

Note

Medium Risk
Major-version cryptography upgrade affects transitive crypto/TLS/auth paths (e.g. via Authlib); low direct code change but warrants regression checks on auth and any PKCS#7 usage.

Overview
Updates envs/calendar_env/uv.lock so the resolved cryptography package moves from 48.0.0 to 50.0.0, including refreshed wheel/sdist pins for all supported platforms.

The re-lock also tweaks unrelated dependency markers (e.g. pandas and secretstorage edges) as a side effect of resolving the graph with the new cryptography release—no application source changes.

50.0.0 includes a security fix (CVE-2026-69247) for PKCS#7 decryption oracles; worth noting if this env decrypts untrusted PKCS#7/S-MIME content via cryptography.

^{Reviewed by Cursor Bugbot for commit d85f80d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[bot-ci-comment]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[cursor]

Alignment Review Report

Automated two-tier review of this Dependabot bump (cryptography 48.0.0 → 50.0.0 in envs/calendar_env). The diff touches a single file — envs/calendar_env/uv.lock — with no Python source changes.

Automated Checks

• Lint: PASS (scoped to this PR). No .py files change, so the PR introduces no formatting/lint findings. I also ran uv lock --check in envs/calendar_env → Resolved 125 packages, confirming the lockfile stays internally consistent with pyproject.toml.
  • Note (out of scope): the repo-wide .claude/hooks/lint.sh reports pre-existing ruff format diffs in ~25 files across other envs (chat_env, opencode_env, pi_env, …). None are in calendar_env and none are touched by this PR — they are pre-existing on main.
• Debug code: CLEAN (scoped to this PR). check-debug.sh only surfaces pre-existing print/TODO statements under src/openenv/; none appear in this diff.

Open RFCs Context

In Review: 000 (project-phases), 001 (abstractions), 002 (env-spec), 003 (MCP), 005 (agentic-harnesses); plus 004 (rubrics); Draft: 010 (echo-env world model). All concern core abstractions, env spec, the MCP/Gym boundary, rewards/rubrics, harnesses, and world modeling. None govern dependency or supply-chain management, so none are implicated by a lockfile bump.

Tier 1: Fixes Required

None.

• cryptography is a transitive dependency (pulled in via secretstorage); it is not pinned in pyproject.toml or requirements.txt, so no manifest needs a matching edit.
• The remaining hunks (pandas, secretstorage marker simplifications) are normal uv lock regeneration churn, not semantic dependency changes.
• Security: upgrading cryptography is security-positive; no credentials or secrets are involved.

Tier 2: Alignment Discussion

Principle Conflicts

None identified. A transitive lockfile bump does not touch the Gymnasium-style API (reset/step/state), the MCP agent boundary, rewards-in-environment, client/server separation, or agent-reset isolation.

RFC Conflicts

None identified. No open or draft RFC covers dependency / supply-chain management.

Summary

• 0 mechanical issues to fix
• 0 alignment points for human review
• 0 RFC conflicts to discuss

Clean, low-risk transitive dependency bump — no blocking concerns.

  

_{Sent by Cursor Automation: Pre-review}

[burtenshaw]

Closing in favor of aggregate env Dependabot PR #1015.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.