Repository navigation
Bump the go group across 1 directory with 2 updates - #136
Merged
Merged
Conversation
Bumps the go group with 2 updates in the / directory: [github.com/beevik/etree](https://github.com/beevik/etree) and [golang.org/x/crypto](https://github.com/golang/crypto). Updates `github.com/beevik/etree` from 1.7.1 to 1.8.0 - [Release notes](https://github.com/beevik/etree/releases) - [Changelog](https://github.com/beevik/etree/blob/main/RELEASE_NOTES.md) - [Commits](beevik/etree@v1.7.1...v1.8.0) Updates `golang.org/x/crypto` from 0.55.0 to 0.56.0 - [Commits](golang/crypto@v0.55.0...v0.56.0) --- updated-dependencies: - dependency-name: github.com/beevik/etree dependency-version: 1.8.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go - dependency-name: golang.org/x/crypto dependency-version: 0.56.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: go ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
This comment has been minimized.
This comment has been minimized.
golang.org/x/crypto 0.56.0 declares go 1.26.0, which raised the go.mod directive above the 1.25 builder image pin and broke the image build: go: go.mod requires go >= 1.26.0 (running go 1.25.14; GOTOOLCHAIN=local) Pin 1.27 to match the go-version: stable used by the Build workflow.
The Docker Image workflow's build job was also named "Build", so it published a check run with the same name as the Build workflow's job. Required status checks match on check-run name only, making the branch ruleset's required "Build" context ambiguous: the PR check list showed Build:FAILURE next to Build:SUCCESS. Rename the Docker job to "Docker Build" (the job key stays 'build', so the publish job's needs: build is unaffected), and widen build.yml's pull_request path filter to Dockerfile and .github/workflows/** so the required check still reports on PRs that touch only those files instead of sitting pending forever.
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 the go group with 2 updates in the / directory: github.com/beevik/etree and golang.org/x/crypto.
Updates
github.com/beevik/etreefrom 1.7.1 to 1.8.0Release notes
Sourced from github.com/beevik/etree's releases.
Changelog
Sourced from github.com/beevik/etree's changelog.
Commits
1850f3eRelease v1.8.0c9eec49Add Remove function to all tokensUpdates
golang.org/x/cryptofrom 0.55.0 to 0.56.0Commits
86efde5ssh: reject unexpected message types on established channelsa6cdac6ssh: drop traffic on undecided channels39dc44essh: don't skip the source-address critical option in CheckCertafebf4cx509roots/fallback/bundle: make subjectsEqual stricter on Go 1.27+89f4e9bx509roots/fallback: update bundle71488c4ssh/knownhosts: compare only public key portions for revocation82adefassh: synchronize unexpected response testc757c98all: upgrade go directive to at least 1.26.0 [generated]593c81assh: correctly ignore pre-banner lines46efc8bacme: add crypto.SignMessage test coverageDependabot 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions