Repository navigation
Bump golang.org/x/crypto from 0.22.0 to 0.52.0 - #65
Merged
robertodauria merged 2 commits intoOct 6, 2026
Merged
Conversation
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.22.0 to 0.52.0. - [Commits](golang/crypto@v0.22.0...v0.52.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-version: 0.52.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
robertodauria
deleted the
dependabot/go_modules/golang.org/x/crypto-0.52.0
branch
October 6, 2026 12:38
nkinkade
added a commit
that referenced
this pull request
Oct 8, 2026
go.mod has required Go 1.25 since the golang.org/x/crypto bump (#65), so the golang:1.20 build image fails at "go get" with "errors parsing go.mod". The Docker Hub automated build has been failing on main since that commit. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
nkinkade
added a commit
that referenced
this pull request
Oct 14, 2026
…er (#70) * uploadbundle: retry failed uploads, then hand files back to the watcher A bundle whose GCS upload failed was logged and dropped: its files stayed on disk but remained in the directory watcher's notified-files map, so the missed-file scan never picked them up again and the data was lost until the next jostler restart. Because annotation2 bundles are closed by age (one per hour) while ndt7 bundles are closed by size, a single transient failure on a BYOS node erased a whole hour of annotations. Each upload (data object, then index) is now retried a few times with exponential backoff. If it still fails, the bundle's files are left on disk but acknowledged to the watcher anyway, so they leave the notified-files map and the periodic missed-file scan re-bundles them once they are older than the configured missed age. Memory is released in the meantime rather than holding re-queued bundles through an outage. Also remove the upload-bundles map entry for age-triggered uploads, whose timer has already fired so nothing else would ever delete it, and add two metrics: jostler_upload_errors_total (failed attempts) and jostler_bundles_deferred_total (bundles handed back after all retries). Fixes #69. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * Dockerfile: build with golang:1.25 go.mod has required Go 1.25 since the golang.org/x/crypto bump (#65), so the golang:1.20 build image fails at "go get" with "errors parsing go.mod". The Docker Hub automated build has been failing on main since that commit. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <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
1 participant
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 golang.org/x/crypto from 0.22.0 to 0.52.0.
Commits
a1c0d99go.mod: update golang.org/x dependencies3c7c869ssh: fix deadlock on unexpected channel responses533fb3fssh: fix source-address critical option bypassabbc44dssh: fix incorrect operator ordere052873ssh: fix infinite loop on large channel writes due to integer overflowb61cf85ssh: enforce user presence verification for security keys9c2cd33ssh: enforce strict limits on DSA key parameters8907318ssh: reject RSA keys with excessively large moduliffd87b4ssh: fix panic when authority callbacks are nil4e7a738ssh: fix deadlock on unexpected global responsesDependabot 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.
This change is