renovate[bot]
c1fe1f9d32
fix(deps): update module github.com/gorilla/mux to v1.8.1
...
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2023-11-05 07:11:57 +00:00
dependabot[bot]
9457549fff
build(deps): bump github.com/vbauerster/mpb/v7 from 7.5.2 to 7.5.3
...
Bumps [github.com/vbauerster/mpb/v7](https://github.com/vbauerster/mpb ) from 7.5.2 to 7.5.3.
- [Release notes](https://github.com/vbauerster/mpb/releases )
- [Commits](https://github.com/vbauerster/mpb/compare/v7.5.2...v7.5.3 )
---
updated-dependencies:
- dependency-name: github.com/vbauerster/mpb/v7
dependency-type: direct:production
update-type: version-update:semver-patch
...
Also bump the go module to 1.17 to be able to compile the new code.
Given containers/common and others already require go 1.17+ we're
safe to go.
Signed-off-by: dependabot[bot] <support@github.com >
Signed-off-by: Valentin Rothberg <vrothberg@redhat.com >
2022-09-13 08:58:22 +02:00
Daniel J Walsh
270c02f308
Bump github.com/gorilla/mux from 1.7.4 to 1.8.0
...
Bumps [github.com/gorilla/mux](https://github.com/gorilla/mux ) from 1.7.4 to 1.8.0.
- [Release notes](https://github.com/gorilla/mux/releases )
- [Commits](https://github.com/gorilla/mux/compare/v1.7.4...v1.8.0 )
Signed-off-by: dependabot-preview[bot] <support@dependabot.com >
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com >
2020-09-02 06:46:20 -04:00
dependabot-preview[bot]
b916263d01
build(deps): bump github.com/gorilla/mux from 1.7.3 to 1.7.4
...
Bumps [github.com/gorilla/mux](https://github.com/gorilla/mux ) from 1.7.3 to 1.7.4.
- [Release notes](https://github.com/gorilla/mux/releases )
- [Commits](https://github.com/gorilla/mux/compare/v1.7.3...v1.7.4 )
Signed-off-by: dependabot-preview[bot] <support@dependabot.com >
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com >
2020-02-12 05:20:50 -05:00
Miloslav Trmač
d3f59bedb3
Update c/image to v4.0.1 and buildah to 1.11.3
...
This requires updating all import paths throughout, and a matching
buildah update to interoperate.
I can't figure out the reason for go.mod tracking
github.com/containers/image v3.0.2+incompatible // indirect
((go mod graph) lists it as a direct dependency of libpod, but
(go list -json -m all) lists it as an indirect dependency),
but at least looking at the vendor subdirectory, it doesn't seem
to be actually used in the built binaries.
Signed-off-by: Miloslav Trmač <mitr@redhat.com >
2019-10-04 20:18:23 +02:00
Valentin Rothberg
d697456dc9
migrate to go-modules
...
Signed-off-by: Valentin Rothberg <rothberg@redhat.com >
2019-06-24 13:20:59 +02:00
Valentin Rothberg
bd40dcfc2b
vendor: update everything
...
* If possible, update each dependency to the latest available version.
* Use releases over commit IDs and avoid vendoring branches.
Signed-off-by: Valentin Rothberg <rothberg@redhat.com >
2019-01-11 13:38:11 +01:00
Matthew Heon
a031b83a09
Initial checkin from CRI-O repo
...
Signed-off-by: Matthew Heon <matthew.heon@gmail.com >
2017-11-01 11:24:59 -04:00
