Repository navigation
chore(deps): bump cryptography from 48.0.1 to 50.0.0 in /agent-governance-python/agent-os/services/cloud-board - #3588
Conversation
Bumps [cryptography](https://github.com/pyca/cryptography) from 48.0.1 to 50.0.0. - [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst) - [Commits](pyca/cryptography@48.0.1...50.0.0) --- updated-dependencies: - dependency-name: cryptography dependency-version: 50.0.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
PR Review Summary
Verdict: AI review comments are untrusted advisory output. The summary reports workflow-generated completion status only, not model-authored pass/fail claims. |
There was a problem hiding this comment.
Pull request overview
Note
Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.
Updates the cloud-board service’s Python dependencies to address a cryptography-related CVE by bumping the pinned cryptography version.
Changes:
- Bump
cryptographyfrom48.0.1to50.0.0inrequirements.txt
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
📦 Dependency diff (SBOM)Comparing main → dependabot/pip/agent-governance-python/agent-os/services/cloud-board/cryptography-50.0.0. ✅ No dependency changes detected. |
The core metapackage's <50.0 cap is disjoint with the dependabot dev-extra widens to >=50.0 (#3607/#3610), so their test matrices die at pip install with ResolutionImpossible before a single test runs. Same shape as the 49-cycle widen (#3070). Compatibility evidence for 50.0.0: the full agent-mesh suite passes under cryptography 50 with this cap lifted (3601 passed; the two failures are sandbox-environment subprocess denials, not crypto), on top of the cloud-board/nexus verification from #3588 (85 tests; no applicable 49/50 breaking changes on Ed25519/AESGCM surfaces). Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
…together (#3621) Dependabot raised the two widens separately (#3607/#3610), but docker-compose-test co-installs every package, so each PR conflicts with the other package's still-capped <50.0 dev extra and neither can go green alone. Land both in one change; dependabot closes its PRs automatically once the manifests move. Compatibility evidence for 50.0.0 is already on record: full agent-mesh suite passes under 50 (3601 tests, incl. all 238 crypto-surface tests), cloud-board/nexus verified in the #3588 review, and the core/marketplace runtime caps were widened in #3615/#3604. Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
|
This is a major |
…ail (#3646) * chore(deps): bump cryptography to 50.0.0 in cloud-board with audit trail Supersedes dependabot #3588: the Dependency Audit Trail gate requires the audit doc inside the bumping PR, which dependabot cannot author for majors. Compatibility evidence in the doc; cooling window elapsed 2026-08-07. Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com> * chore(deps): refresh the stale CVE comment on the cryptography pin Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com> * chore(deps): sync cloud-board lockfile to cryptography 50.0.0 requirements.txt pins cryptography==50.0.0 but requirements.lock still pinned 46.0.5. Bump the lock entry to 50.0.0 with the full set of 46 upstream PyPI sha256 hashes (verified against the /pypi/cryptography/ 50.0.0/json artifact digests). Addresses the review note that the lock lagged the requirement. Signed-off-by: Prayag Upadhyay <prayag.upd@gmail.com> * chore(spell-check): allowlist cloud-board cryptography audit terms The cryptography 50.0.0 audit doc introduces standard crypto vocabulary (AESGCM, Bleichenbacher, FFDH, OCSP, SPKI) that cspell's bundled dictionaries do not recognize, failing the Spell-check job. Add them to the repo terms allowlist so the audit doc passes deterministically. Signed-off-by: Prayag Upadhyay <prayag.upd@gmail.com> --------- Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com> Signed-off-by: Prayag Upadhyay <prayag.upd@gmail.com> Co-authored-by: Prayag Upadhyay <prayag.upd@gmail.com>
Bumps cryptography from 48.0.1 to 50.0.0.
Changelog
Sourced from cryptography's changelog.
... (truncated)
Commits
dcb7050Prepare for 50.0.0 release (#15372)53fccd9Don't leak how PKCS#7 encryptedKey decryption failed (#15369)d472f97Addfrom __future__ import annotationsto all src/ Python files (#15371)908773dBump downstream dependencies in CI (#15368)2cc07ccBump BoringSSL, OpenSSL, AWS-LC in CI (#15367)c94ede9chore(deps): bump ruff from 0.16.0 to 0.16.1 (#15366)67a8308chore(deps): bump virtualenv from 21.7.0 to 21.7.1 (#15365)95018ffRelease the GIL in one-shot AEAD encrypt/decrypt (#15361)6954733Release the GIL during DH and DSA parameter generation (#15364)6893b94Import _serialization instead of serialization in x509/extensions (#15363)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.