Repository housekeeping - #58
Merged
Merged
Conversation
go 1.24 removed the x509sha1 GODEBUG option, so the SHA1 test cases fail on 1.24 and newer.
azazeal
marked this pull request as ready for review
July 15, 2026 12:46
hslatman
previously approved these changes
Jul 15, 2026
hslatman
approved these changes
Jul 15, 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.
The weekly
Code Scan Cronworkflow has been failing since at least May: the sharedcode-scan.ymldefaults CodeQL's build command toV=1 make build, and this repo'sMakefilehas nobuildtarget. This PR fixes that by telling CodeQL to build with a plaingo build ./..., the same fix already in use inbackend.It also does some housekeeping: pins all actions to their current versions by checksum, stops CI from running twice for PRs, expands the
dependabotconfig to also cover GitHub Actions, and adds an.editorconfigfile.Finally, no code is touched in this PR so there's no need for a new release.