Repository navigation
chore(deps): bump the minor group with 2 updates - #121
dependabot[bot] wants to merge 3 commits into
Conversation
Bumps the minor group with 2 updates: [github.com/containifyci/engine-ci](https://github.com/containifyci/engine-ci) and [github.com/stretchr/testify](https://github.com/stretchr/testify). Updates `github.com/containifyci/engine-ci` from 0.42.9 to 0.46.1 - [Release notes](https://github.com/containifyci/engine-ci/releases) - [Commits](containifyci/engine-ci@v0.42.9...v0.46.1) Updates `github.com/stretchr/testify` from 1.11.1 to 1.12.1 - [Release notes](https://github.com/stretchr/testify/releases) - [Commits](stretchr/testify@v1.11.1...v1.12.1) --- updated-dependencies: - dependency-name: github.com/containifyci/engine-ci dependency-version: 0.46.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor - dependency-name: github.com/stretchr/testify dependency-version: 1.12.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'failure' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
4 similar comments
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'failure' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'failure' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'failure' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'failure' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
18 similar comments
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go podman / Build with ContainifyCI podman' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
10 similar comments
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
|
Note This Pull Request can't be approved by DuneBot because the following status check failed. Status 'build-engine-ci / Build Go docker / Build with ContainifyCI docker' has a different state 'cancelled' then is not success, neutral, skipped, completed, in_progress or queued ❓ Got questions? You can trigger DuneBot reprocessing by closing and reopen the Pull Request. This PR comment was generated by DuneBot |
…n replaces The dependabot bump to engine-ci v0.46.1 pulls in podman v6.1.0 (go.podman.io/podman/v6), which uses runtime-spec v1.3.0 natively where spec.LinuxPids.Limit is *int64. The three replace directives inherited from the podman v5 era pinned runtime-spec to v1.2.1 (where Limit is int64), causing a typecheck failure in podman/v6@v6.1.0/pkg/specgen/resources_linux.go: cannot use &limit (value of type *int64) as int64 value in struct literal This cascaded into all container.Container methods being reported as undefined on *MavenContainer in pkg/maven/maven.go, failing the build-engine-ci / Build Go podman check on PR containifyci#121. engine-ci v0.46.1 no longer carries these replaces (they are commented out there), so mirror that and let podman v6 resolve the versions natively.
fix(deps): remove stale runtime-spec pins breaking podman v6 (PR #121)
|
Looks like these dependencies are no longer updatable, so this is no longer needed. |
Bumps the minor group with 2 updates: github.com/containifyci/engine-ci and github.com/stretchr/testify.
Updates
github.com/containifyci/engine-cifrom 0.42.9 to 0.46.1Release notes
Sourced from github.com/containifyci/engine-ci's releases.
... (truncated)
Commits
a18aee4fix(utils): redact secret identifiers from logs in environment.go (#555)9de4ff0chore(deps): update base images and pinned packages in Dockerfiles (#553)3729c7echore(deps): bump github.com/stretchr/testify (#552)93e4265chore(deps): bump github.com/stretchr/testify (#551)d747139chore(deps): update to latest versions (#550)1c4e886refactor(cri): migrate from docker/docker flat module to moby/moby (#549)bf507f6chore(deps): bump docker/setup-buildx-action from 3 to 4 (#548)ad4b405chore(deps): bump docker/build-push-action from 6 to 7 (#547)c6e656cchore(deps): bump docker/setup-qemu-action from 3 to 4 (#546)b3c2590chore(deps): bump containifyci/.github in the minor group (#545)Updates
github.com/stretchr/testifyfrom 1.11.1 to 1.12.1Release notes
Sourced from github.com/stretchr/testify's releases.
... (truncated)
Commits
959dbdaMerge pull request #1935 from harryzcy/yaml-update9bb7176Update go.yaml.in/yaml/v3 to v3.0.5001eb79Merge pull request #1905 from Kentzo/patch-1ad40f38Merge pull request #1906 from stretchr/dependabot/github_actions/actions/chec...3bae017build(deps): bump actions/checkout from 6.0.2 to 6.0.3f8c01f3mock: Mock.Return does not exist anymore12f8b56Merge pull request #1563 from stretchr/make-AssertionFunc-types-aliasesa11649eassert: make *AssertionFunc type just aliasesdc20f41Merge pull request #1890 from stretchr/dolmen/codegen-modernize098f8d7_codegen: use strings.BuilderDependabot 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