Bump pyasn1 from 0.6.3 to 0.6.4 - #728
Merged
Merged
Conversation
Bumps [pyasn1](https://github.com/pyasn1/pyasn1) from 0.6.3 to 0.6.4. - [Release notes](https://github.com/pyasn1/pyasn1/releases) - [Changelog](https://github.com/pyasn1/pyasn1/blob/main/CHANGES.rst) - [Commits](pyasn1/pyasn1@v0.6.3...v0.6.4) --- updated-dependencies: - dependency-name: pyasn1 dependency-version: 0.6.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
🔵 Review postedLast updated: 2026-08-01 11:22 UTC |
rtibblesbot
approved these changes
Aug 1, 2026
rtibblesbot
left a comment
Contributor
There was a problem hiding this comment.
PR #728 bumps pyasn1 0.6.3 → 0.6.4 in uv.lock — a patch-level security release.
- Semver risk: patch
- Dependency type: transitive, optional production extra (
google_drive→google-auth→pyasn1-modules→pyasn1); not in basedependencies - Security fixes: three DoS-class CVEs — CVE-2026-59885 (quadratic-time OID/RELATIVE-OID decoding; decoded values unchanged), CVE-2026-59884 (BER long-form tag IDs now capped at 20 octets, longer ones raise
PyAsn1Error), CVE-2026-59886 (Real.__float__()raisesOverflowErrorpromptly instead of grinding; base-10 mantissa normalization now exact) - Breaking changes: none declared. Two intentional hardening changes: pathological >20-octet tag IDs are rejected, and
Real→floatresults above 2**53 mantissa are now exact rather than lossy. - Peer/transitive changes: none —
pyasn1remains dependency-free,pyasn1-modulesstays at 0.4.2 with an unpinnedpyasn1requirement - Code changes required: none — no
pyasn1usage in ricecooker source; all use is insidegoogle-authparsing trusted service-account key material - CI: passing (11/11 runs on
22ad28a)
Lockfile diff is 3 lines confined to the pyasn1 block — version, sdist hash, wheel hash. No transitive churn smuggled in.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Ran a dependency-update review pipeline over the version bump:
- Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
- Extracted the changelog and release notes across the version range
- Assessed compatibility with this project's usage and whether any code changes are required
- Treated CI as the primary safety net
- Scaled the review depth to the update's risk
- Chose the verdict from semver risk, changelog findings, and CI status
rtibbles
approved these changes
Aug 3, 2026
rtibbles
left a comment
Member
There was a problem hiding this comment.
No concerns from changelog, tests all green.
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 pyasn1 from 0.6.3 to 0.6.4.
Release notes
Sourced from pyasn1's releases.
Changelog
Sourced from pyasn1's changelog.
Commits
72e4803Prepare release 0.6.40c19eebPin PyPI publish action to immutable commit (#113)45bdb19Merge commit from fork628e36eMerge commit from forke60c691Merge commit from forkDependabot 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.