build(deps): bump github.com/aws/aws-lambda-go from 1.27.0 to 1.47.0 #896
Conversation
This file contains 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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
Bumps [github.com/aws/aws-lambda-go](https://github.com/aws/aws-lambda-go) from 1.27.0 to 1.47.0. - [Release notes](https://github.com/aws/aws-lambda-go/releases) - [Commits](aws/aws-lambda-go@v1.27.0...v1.47.0) --- updated-dependencies: - dependency-name: github.com/aws/aws-lambda-go dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/go_modules/github.com/aws/aws-lambda-go-1.47.0
branch
from
285825d
to
69887b4
Compare
Pull Request Test Coverage Report for Build 11076Details
💛 - Coveralls |
|
Uh oh! It seems like dependabot is quite happy to re-introduce the duplicate copy of |
jmhodges
added a commit
that referenced
this pull request
May 2, 2024
This was causing surprises for devs making changes in that package and hitting a variety of build problems when they realized they hadn't updated the top-level go.mod. And other hacks failed to be kept up (see #896 (comment) ). The only external user of verifier/contentsignature was the mozilla-vpn-client and @oskirby (a maintainer of it) tells us they've been using a rust version for a while now. Clients also could just use the autograph repo's versioning instead. Can be confirmed with this search: https://github.com/search?q=autograph%2Fverifier%2Fcontentsignature&type=code
|
PR up to fix the verifier/contentsignature problem: #899 |
jmhodges
added a commit
that referenced
this pull request
May 3, 2024
This was causing surprises for devs making changes in that package and hitting a variety of build problems when they realized they hadn't updated the top-level go.mod. And other hacks failed to be kept up (see #896 (comment) ). The only external user of verifier/contentsignature was the mozilla-vpn-client and @oskirby (a maintainer of it) tells us they've been using a rust version for a while now. Clients also could just use the autograph repo's versioning instead. Can be confirmed with this search: https://github.com/search?q=autograph%2Fverifier%2Fcontentsignature&type=code
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 github.com/aws/aws-lambda-go from 1.27.0 to 1.47.0.
Release notes
Sourced from github.com/aws/aws-lambda-go's releases.
... (truncated)
Commits
8e674daAdd 1.22 to tests (#557)90a3af7Handle disconnect route of Websocket (#548)de51f68Fix compile error in sample code for S3ObjectLambdaEvent (#551)eae55b8Add S3 Batch Operations 2.0 Schema Fields to S3BatchJob/S3BatchJobTask (#550)58da2ccPlumb error info to X-ray (#544)3a93ed1lambdaurl: Populate RemoteAddr with SourceIP (#546)cce0845linter config: reformat the lists (#545)c5ef6f1'Building your function' README updates (#543)501c2f3Add S3ObjectLambdaEvent (#536)50dbfb1[479] CloudWatchEvent renamed to EventBridgeEvent (#537)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 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)