chore(deps): bump cryptography from 48.0.1 to 50.0.0 - #362
Merged
Conversation
Contributor
|
Dependabot (@dependabot) rebase |
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>
dependabot
Bot
force-pushed
the
dependabot/uv/cryptography-50.0.0
branch
from
August 7, 2026 14:21
588ed1c to
fa619af
Compare
Paulo Lacerda (placerda)
added a commit
that referenced
this pull request
Aug 7, 2026
…p below 2.0 (#385) * chore(deps): bump mcp from 1.27.1 to 1.28.1 (#356) Bumps [mcp](https://github.com/modelcontextprotocol/python-sdk) from 1.27.1 to 1.28.1. - [Release notes](https://github.com/modelcontextprotocol/python-sdk/releases) - [Changelog](https://github.com/modelcontextprotocol/python-sdk/blob/main/RELEASE.md) - [Commits](modelcontextprotocol/python-sdk@v1.27.1...v1.28.1) --- updated-dependencies: - dependency-name: mcp dependency-version: 1.28.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump cryptography from 48.0.1 to 50.0.0 (#362) 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> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): pin mcp floor to 1.28.1 and document Dependabot security-update targeting Raises the mcp extra floor to >=1.28.1 (matching the version synced from main) and keeps the <2 upper bound: mcp 2.0.0 is a breaking rewrite that replaces FastMCP with MCPServer, and src/agentops/mcp/server.py targets the 1.x API. Also documents in .github/dependabot.yml why security PRs land on main despite target-branch: develop, and the correct way to re-cut them. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Paulo Lacerda (placerda)
added a commit
that referenced
this pull request
Aug 7, 2026
Dependabot security updates always target the default branch and ignore `target-branch: develop` in dependabot.yml. Two of them (#356 mcp, #362 cryptography) squash-merged straight into `main`, leaving `main` two commits ahead of `develop`. Their content was already cherry-picked into `develop` via #385, and `develop` has since moved further ahead: package develop main aiohttp 3.14.3 3.14.1 cryptography 50.0.0 50.0.0 mcp 1.28.1 1.28.1 nltk 3.10.0 3.9.4 So `develop` is a strict superset. What was missing was only the ancestry link, and that gap is not cosmetic: `git merge-tree origin/main origin/develop` reproduces a real CONFLICT in `uv.lock`. The next `release/vX.Y.Z` -> `main` merge would have hit that conflict. This uses `-s ours` deliberately. Both main-only commits touch `uv.lock` and nothing else, and `develop` already carries equal-or-newer versions of every package they bumped, so discarding their tree loses nothing. The merge exists to advance the merge-base, not to move files. Verified after merging: `git diff HEAD origin/develop` is empty (no file changed) and `git log origin/develop..origin/main` is empty (ancestry closed). Refs #366 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: bcb9c0b6-d506-46dc-90d2-8120413166ee
This was referenced Aug 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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)