-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(deps): bump dagger.io/dagger from 0.14.0 to 0.15.1 in /action #482
base: main
Are you sure you want to change the base?
build(deps): bump dagger.io/dagger from 0.14.0 to 0.15.1 in /action #482
Conversation
8afa334
to
79d1504
Compare
79d1504
to
59ddf84
Compare
Looks like the only failing check here is the CVE check on an indirect dep so far. |
If the |
I just bumped that particular indirect one as well, locally it was building just fine with it |
Looks like it's getting stuck somewhere, likely #476 I suppose? |
Same thing happens locally. Let me check if the timeout of 5s resolves it and I'll update both PRs. |
#476 does not resolve it, it just makes it fail faster. |
Must be some kind of breaking change in dagger |
Yep, adding the timeout un-stucks the test. I'll try to find out what was changed for dagger to behave different here now. |
|
So, basically, I think that it would be better to drop the whole SSH feature and replace it with #269. Especially if fixing the SSH will take long time, it might be better investment. Do you know how severe is the security 12 issue? The previous one security issue 11 had minimal impact since it was affecting only testing. |
Bumps [dagger.io/dagger](https://github.com/dagger/dagger-go-sdk) from 0.14.0 to 0.15.1. - [Changelog](https://github.com/dagger/dagger-go-sdk/blob/main/CHANGELOG.md) - [Commits](dagger/dagger-go-sdk@v0.14.0...v0.15.1) --- updated-dependencies: - dependency-name: dagger.io/dagger dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
f85430e
to
f25dd9e
Compare
Bumps dagger.io/dagger from 0.14.0 to 0.15.1.
Changelog
Sourced from dagger.io/dagger's changelog.
Commits
4303d99
chore: prep for v0.15.1 (#9183)92069b3
upgrade golang.org/x/crypto dep to avoid CVE (#9172)6eeb37b
chore: update release date for v0.15.0 (#9166)d665c65
chore: prep for v0.15.0 (#9158)38c89e6
shell: reimplement module loading and execution according to new model (#9097)be9da24
fix(engine): use default args for starting container as service (#8865)682852f
Filesync performance improvements (#8818)efadaf7
chore: bump next version to v0.15.0 (#9073)ff2070a
bump seconv to v1.25.0 to match otel v1.27.0 (#9067)c209a4d
Preserve ExecError Stdout/Stderr, just don't show it (#9033)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 rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will 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 version
will 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 dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)