Git-Mirrors/constellation
1
0
Fork 0
mirror of https://github.com/edgelesssys/constellation.git synced 2024-12-14 18:34:31 -05:00
Code Issues Packages Projects Releases Wiki Activity
4f1768e660
constellation/hack/tools/go.mod

57 lines
2.3 KiB
Modula-2
Raw Normal View History

tools: version tools in tools.go Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-14 12:18:33 -04:00
module github.com/edgelesssys/constellation/v2/hack/tools
deps: update Go to 1.22.0
2024-02-19 12:20:08 -05:00
go 1.22
tools: version tools in tools.go Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-14 12:18:33 -04:00
bazel: add license checks to //:check target (#1509) Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-27 04:42:30 -04:00
require (
github.com/google/go-licenses v1.6.0
ci: introduce keep-sorted (#2836) Long lists of items in source code or config can be hard to work with as a human, most problematic being out-of-order entries in an otherwise ordered list. This is where keep-sorted comes to the rescue: we can leave two little comments on every listing we care about, and keep-sorted ensures that the listing stays in order. This commit also applied keep-sorted to the CODEOWNERS file, hopefully demonstrating its usefulness to some extent. I'd expect more uses for keep-sorted to be discovered organically over time. keep-sorted is super fast, so it should not be a problem to add it to the //:tidy target, even if we scan all files in the code base. On my MacBook: $ time (find . -not -path "./.git/*" -type f | sort | xargs "${keep_sorted}" --mode fix) real 0m0.249s user 0m0.124s sys 0m0.129s
2024-01-30 08:39:49 -05:00
github.com/google/keep-sorted v0.3.0
deps: update module github.com/katexochen/sh/v3 to v3.7.0 (#2013) Co-authored-by: Malte Poll <1780588+malt3@users.noreply.github.com>
2023-07-05 09:23:24 -04:00
github.com/katexochen/sh/v3 v3.7.0
deps: update all Go deps
2024-02-21 04:18:52 -05:00
golang.org/x/tools v0.18.0
deps: update module golang.org/x/vuln to v1.0.1 (#2365) * deps: update module golang.org/x/vuln to v1.0.1 * deps: tidy all modules --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: edgelessci <edgelessci@users.noreply.github.com>
2023-09-29 15:45:42 -04:00
golang.org/x/vuln v1.0.1
bazel: add license checks to //:check target (#1509) Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-27 04:42:30 -04:00
)
tools: version tools in tools.go Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-14 12:18:33 -04:00
require (
deps: update all Go deps
2024-02-21 04:18:52 -05:00
github.com/Microsoft/go-winio v0.6.1 // indirect
ci: introduce keep-sorted (#2836) Long lists of items in source code or config can be hard to work with as a human, most problematic being out-of-order entries in an otherwise ordered list. This is where keep-sorted comes to the rescue: we can leave two little comments on every listing we care about, and keep-sorted ensures that the listing stays in order. This commit also applied keep-sorted to the CODEOWNERS file, hopefully demonstrating its usefulness to some extent. I'd expect more uses for keep-sorted to be discovered organically over time. keep-sorted is super fast, so it should not be a problem to add it to the //:tidy target, even if we scan all files in the code base. On my MacBook: $ time (find . -not -path "./.git/*" -type f | sort | xargs "${keep_sorted}" --mode fix) real 0m0.249s user 0m0.124s sys 0m0.129s
2024-01-30 08:39:49 -05:00
github.com/Workiva/go-datastructures v1.0.53 // indirect
deps: update all Go deps
2024-02-21 04:18:52 -05:00
github.com/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc // indirect
github.com/emirpasic/gods v1.18.1 // indirect
github.com/frankban/quicktest v1.14.6 // indirect
github.com/go-logr/logr v1.4.1 // indirect
bazel: add license checks to //:check target (#1509) Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-27 04:42:30 -04:00
github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da // indirect
deps: update all Go deps
2024-02-21 04:18:52 -05:00
github.com/google/go-cmp v0.6.0 // indirect
bazel: add license checks to //:check target (#1509) Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-27 04:42:30 -04:00
github.com/google/licenseclassifier v0.0.0-20210722185704-3043a050f148 // indirect
tools: version tools in tools.go Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-14 12:18:33 -04:00
github.com/google/renameio/v2 v2.0.0 // indirect
deps: update all Go deps
2024-02-21 04:18:52 -05:00
github.com/inconshreveable/mousetrap v1.1.0 // indirect
bazel: add license checks to //:check target (#1509) Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-27 04:42:30 -04:00
github.com/jbenet/go-context v0.0.0-20150711004518-d14ea06fba99 // indirect
deps: update all Go deps
2024-02-21 04:18:52 -05:00
github.com/kevinburke/ssh_config v1.2.0 // indirect
ci: introduce keep-sorted (#2836) Long lists of items in source code or config can be hard to work with as a human, most problematic being out-of-order entries in an otherwise ordered list. This is where keep-sorted comes to the rescue: we can leave two little comments on every listing we care about, and keep-sorted ensures that the listing stays in order. This commit also applied keep-sorted to the CODEOWNERS file, hopefully demonstrating its usefulness to some extent. I'd expect more uses for keep-sorted to be discovered organically over time. keep-sorted is super fast, so it should not be a problem to add it to the //:tidy target, even if we scan all files in the code base. On my MacBook: $ time (find . -not -path "./.git/*" -type f | sort | xargs "${keep_sorted}" --mode fix) real 0m0.249s user 0m0.124s sys 0m0.129s
2024-01-30 08:39:49 -05:00
github.com/mattn/go-colorable v0.1.13 // indirect
github.com/mattn/go-isatty v0.0.20 // indirect
bazel: add license checks to //:check target (#1509) Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-27 04:42:30 -04:00
github.com/mitchellh/go-homedir v1.1.0 // indirect
github.com/otiai10/copy v1.6.0 // indirect
tools: version tools in tools.go Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-14 12:18:33 -04:00
github.com/pkg/diff v0.0.0-20210226163009-20ebb0f2a09e // indirect
deps: update all Go deps
2024-02-21 04:18:52 -05:00
github.com/rogpeppe/go-internal v1.12.0 // indirect
ci: introduce keep-sorted (#2836) Long lists of items in source code or config can be hard to work with as a human, most problematic being out-of-order entries in an otherwise ordered list. This is where keep-sorted comes to the rescue: we can leave two little comments on every listing we care about, and keep-sorted ensures that the listing stays in order. This commit also applied keep-sorted to the CODEOWNERS file, hopefully demonstrating its usefulness to some extent. I'd expect more uses for keep-sorted to be discovered organically over time. keep-sorted is super fast, so it should not be a problem to add it to the //:tidy target, even if we scan all files in the code base. On my MacBook: $ time (find . -not -path "./.git/*" -type f | sort | xargs "${keep_sorted}" --mode fix) real 0m0.249s user 0m0.124s sys 0m0.129s
2024-01-30 08:39:49 -05:00
github.com/rs/zerolog v1.31.0 // indirect
deps: update all Go deps
2024-02-21 04:18:52 -05:00
github.com/sergi/go-diff v1.3.1 // indirect
github.com/spf13/cobra v1.8.0 // indirect
bazel: add license checks to //:check target (#1509) Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-27 04:42:30 -04:00
github.com/spf13/pflag v1.0.5 // indirect
github.com/src-d/gcfg v1.4.0 // indirect
deps: update all Go deps
2024-02-21 04:18:52 -05:00
github.com/stretchr/testify v1.8.4 // indirect
github.com/xanzy/ssh-agent v0.3.3 // indirect
go.opencensus.io v0.24.0 // indirect
golang.org/x/crypto v0.19.0 // indirect
golang.org/x/exp v0.0.0-20240213143201-ec583247a57a // indirect
golang.org/x/mod v0.15.0 // indirect
golang.org/x/net v0.21.0 // indirect
golang.org/x/sync v0.6.0 // indirect
golang.org/x/sys v0.17.0 // indirect
golang.org/x/term v0.17.0 // indirect
ci: introduce keep-sorted (#2836) Long lists of items in source code or config can be hard to work with as a human, most problematic being out-of-order entries in an otherwise ordered list. This is where keep-sorted comes to the rescue: we can leave two little comments on every listing we care about, and keep-sorted ensures that the listing stays in order. This commit also applied keep-sorted to the CODEOWNERS file, hopefully demonstrating its usefulness to some extent. I'd expect more uses for keep-sorted to be discovered organically over time. keep-sorted is super fast, so it should not be a problem to add it to the //:tidy target, even if we scan all files in the code base. On my MacBook: $ time (find . -not -path "./.git/*" -type f | sort | xargs "${keep_sorted}" --mode fix) real 0m0.249s user 0m0.124s sys 0m0.129s
2024-01-30 08:39:49 -05:00
golang.org/x/text v0.14.0 // indirect
deps: update protobuf to v1.33.0
2024-03-06 07:37:11 -05:00
google.golang.org/protobuf v1.33.0 // indirect
deps: update all Go deps
2024-02-21 04:18:52 -05:00
gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c // indirect
bazel: add license checks to //:check target (#1509) Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-27 04:42:30 -04:00
gopkg.in/src-d/go-billy.v4 v4.3.2 // indirect
gopkg.in/src-d/go-git.v4 v4.13.1 // indirect
gopkg.in/warnings.v0 v0.1.2 // indirect
deps: update all Go deps
2024-02-21 04:18:52 -05:00
k8s.io/klog/v2 v2.120.1 // indirect
tools: version tools in tools.go Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-03-14 12:18:33 -04:00
mvdan.cc/editorconfig v0.2.0 // indirect
)
Reference in New Issue Copy Permalink