Bump cryptography from 36.0.0 to 39.0.1 - #1
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [cryptography](https://github.com/pyca/cryptography) from 36.0.0 to 39.0.1. - [Release notes](https://github.com/pyca/cryptography/releases) - [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst) - [Commits](pyca/cryptography@36.0.0...39.0.1) --- updated-dependencies: - dependency-name: cryptography dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
nficano
added a commit
that referenced
this pull request
Sep 3, 2026
A bare arithmetic command -- ((x++)), ((x--)), ((v = expr)) -- returns exit
status 1 whenever the expression evaluates to 0. Every script here runs
`set -Eeuo pipefail` with `trap script.cleanup SIGINT SIGTERM ERR EXIT`, so
that status fires the ERR trap and kills the script silently with no output.
This broke the screenshot -> S3 -> clipboard folder action for months:
nanoid: ((idx = val & msk)) died whenever a random byte masked to index 0,
i.e. 1/64 per byte drawn -- measured 55 failures / 400 runs (~12%).
s3-upload: ((attempt++)) returns the pre-increment value 0 on the first
iteration, so the 10-attempt retry loop died on retry #1 instead
of covering for nanoid.
Net effect: s3-upload exited non-zero ~12% of the time, the Automator action's
`if url=$(s3-upload ...)` never entered its body, and nothing was copied to the
clipboard or moved to Trash. Confirmed live with a diagnostic ERR trap:
ERRTRAP cmd=[((idx = val & msk))] rc=1 shellopts=ehuBE
nanoid now measures 0 failures / 400 while still emitting index-0 characters in
51/400 IDs, so the zero case is handled rather than avoided.
Also pass -l "$id_len" to nanoid: S3_UPLOAD_LINK_ID_LENGTH was validated and
then ignored, so IDs were always 8 chars instead of the documented 12.
The remaining 13 sites (bin/net, lib/bash/{queue,exceptions,script,ui/core,
yaml,loaders/shimmer}) are latent rather than confirmed-live; the rewrite only
discards an unused exit status, so it is behaviour-identical either way.
`--help` across all 25 bin/ scripts matches the HEAD baseline exactly.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 36.0.0 to 39.0.1.
Changelog
Sourced from cryptography's changelog.
... (truncated)
Commits
d6951dcchangelog + security fix backport (#8231)138da90workaround scapy bug in downstream tests (#8218) (#8228)69527bcbookworm is py311 now (#8200)111deefbackport main branch CI to 39.0.x (#8153)338a65a39.0.0 version bump (#7954)84a3cd7automatically download and upload circleci wheels (#7949)525c0b3Type annotate release.py (#7951)46d2a94Use the latest 3.10 release when wheel building (#7953)f150dc1fix CI to work with ubuntu 22.04 (#7950)8867724fix README for python3 (#7947)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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.