Infrastructure/imageproxy
0
Fork 0
mirror of https://github.com/willnorris/imageproxy.git synced 2024-12-16 21:56:43 -05:00
Code Issues Activity
imageproxy/go.mod

77 lines
3.5 KiB
Modula-2
Raw Normal View History

switch to use go module support versions of all dependencies remain the same, but now use `go mod` to manage them rather than govendor. This does result in a few extra files being checked in, since govendor would ignore non-build files and go mod does not.
2018-09-15 02:38:09 -05:00
module willnorris.com/go/imageproxy
go.mod: update modules
2024-05-08 23:15:03 -05:00
go 1.21
go.mod: set go version to 1.17 This is not a new requirement... I started using 1.17 features at some point in the past (as indicated in the CI tests). I just missed declaring that requirement in the go.mod file. With go1.17, the structure of the go.mod files changes a bit, but this shouldn't actually have any actual changes in the dependency tree.
2023-01-31 23:23:50 -05:00
require (
go.mod: update modules
2024-05-08 23:15:03 -05:00
cloud.google.com/go/storage v1.40.0
go.mod: set go version to 1.17 This is not a new requirement... I started using 1.17 features at some point in the past (as indicated in the CI tests). I just missed declaring that requirement in the go.mod file. With go1.17, the structure of the go.mod files changes a bit, but this shouldn't actually have any actual changes in the dependency tree.
2023-01-31 23:23:50 -05:00
github.com/PaulARoy/azurestoragecache v0.0.0-20170906084534-3c249a3ba788
go.mod: update modules
2024-05-08 23:15:03 -05:00
github.com/aws/aws-sdk-go v1.52.5
go.mod: set go version to 1.17 This is not a new requirement... I started using 1.17 features at some point in the past (as indicated in the CI tests). I just missed declaring that requirement in the go.mod file. With go1.17, the structure of the go.mod files changes a bit, but this shouldn't actually have any actual changes in the dependency tree.
2023-01-31 23:23:50 -05:00
github.com/die-net/lrucache v0.0.0-20220628165024-20a71bc65bf1
github.com/disintegration/imaging v1.6.2
github.com/fcjr/aia-transport-go v1.2.2
go.mod: update modules
2024-05-08 23:15:03 -05:00
github.com/gomodule/redigo v1.9.2
go.mod: set go version to 1.17 This is not a new requirement... I started using 1.17 features at some point in the past (as indicated in the CI tests). I just missed declaring that requirement in the go.mod file. With go1.17, the structure of the go.mod files changes a bit, but this shouldn't actually have any actual changes in the dependency tree.
2023-01-31 23:23:50 -05:00
github.com/gregjones/httpcache v0.0.0-20190611155906-901d90724c79
github.com/muesli/smartcrop v0.3.0
github.com/peterbourgon/diskv v0.0.0-20171120014656-2973218375c3
go.mod: update modules
2024-05-08 23:15:03 -05:00
github.com/prometheus/client_golang v1.19.0
go.mod: set go version to 1.17 This is not a new requirement... I started using 1.17 features at some point in the past (as indicated in the CI tests). I just missed declaring that requirement in the go.mod file. With go1.17, the structure of the go.mod files changes a bit, but this shouldn't actually have any actual changes in the dependency tree.
2023-01-31 23:23:50 -05:00
github.com/rwcarlsen/goexif v0.0.0-20190401172101-9e8deecbddbd
go.mod: update modules
2024-05-08 23:15:03 -05:00
golang.org/x/image v0.16.0
go.mod: set go version to 1.17 This is not a new requirement... I started using 1.17 features at some point in the past (as indicated in the CI tests). I just missed declaring that requirement in the go.mod file. With go1.17, the structure of the go.mod files changes a bit, but this shouldn't actually have any actual changes in the dependency tree.
2023-01-31 23:23:50 -05:00
willnorris.com/go/gifresize v1.0.0
)
switch to use go module support versions of all dependencies remain the same, but now use `go mod` to manage them rather than govendor. This does result in a few extra files being checked in, since govendor would ignore non-build files and go mod does not.
2018-09-15 02:38:09 -05:00
require (
go.mod: update modules
2024-05-08 23:15:03 -05:00
cloud.google.com/go v0.113.0 // indirect
cloud.google.com/go/auth v0.4.0 // indirect
cloud.google.com/go/auth/oauth2adapt v0.2.2 // indirect
cloud.google.com/go/compute/metadata v0.3.0 // indirect
cloud.google.com/go/iam v1.1.8 // indirect
bump go version to 1.18 and update deps
2023-08-02 10:23:11 -05:00
github.com/Azure/azure-sdk-for-go v68.0.0+incompatible // indirect
go.mod: set go version to 1.17 This is not a new requirement... I started using 1.17 features at some point in the past (as indicated in the CI tests). I just missed declaring that requirement in the go.mod file. With go1.17, the structure of the go.mod files changes a bit, but this shouldn't actually have any actual changes in the dependency tree.
2023-01-31 23:23:50 -05:00
github.com/Azure/go-autorest v14.2.0+incompatible // indirect
bump go version to 1.18 and update deps
2023-08-02 10:23:11 -05:00
github.com/Azure/go-autorest/autorest v0.11.29 // indirect
github.com/Azure/go-autorest/autorest/adal v0.9.23 // indirect
go.mod: set go version to 1.17 This is not a new requirement... I started using 1.17 features at some point in the past (as indicated in the CI tests). I just missed declaring that requirement in the go.mod file. With go1.17, the structure of the go.mod files changes a bit, but this shouldn't actually have any actual changes in the dependency tree.
2023-01-31 23:23:50 -05:00
github.com/Azure/go-autorest/autorest/date v0.3.0 // indirect
cleanup unused module entries
2020-09-10 02:53:01 -05:00
github.com/Azure/go-autorest/autorest/to v0.4.0 // indirect
go.mod: set go version to 1.17 This is not a new requirement... I started using 1.17 features at some point in the past (as indicated in the CI tests). I just missed declaring that requirement in the go.mod file. With go1.17, the structure of the go.mod files changes a bit, but this shouldn't actually have any actual changes in the dependency tree.
2023-01-31 23:23:50 -05:00
github.com/Azure/go-autorest/logger v0.2.1 // indirect
github.com/Azure/go-autorest/tracing v0.6.0 // indirect
github.com/beorn7/perks v1.0.1 // indirect
go.mod: update modules
2024-05-08 23:15:03 -05:00
github.com/cespare/xxhash/v2 v2.3.0 // indirect
go.mod: update indirect dependencies
2021-06-23 13:40:07 -05:00
github.com/dnaeon/go-vcr v1.2.0 // indirect
go.mod: update modules
2024-05-08 23:15:03 -05:00
github.com/felixge/httpsnoop v1.0.4 // indirect
github.com/go-logr/logr v1.4.1 // indirect
github.com/go-logr/stdr v1.2.2 // indirect
bump go version to 1.18 and update deps
2023-08-02 10:23:11 -05:00
github.com/gofrs/uuid v4.4.0+incompatible // indirect
github.com/golang-jwt/jwt/v4 v4.5.0 // indirect
update dependencies
2022-02-16 14:00:53 -05:00
github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da // indirect
go.mod: update modules
2024-05-08 23:15:03 -05:00
github.com/golang/protobuf v1.5.4 // indirect
go.mod: bump all deps
2022-11-14 14:58:59 -05:00
github.com/google/btree v1.1.2 // indirect
go.mod: update modules
2024-05-08 23:15:03 -05:00
github.com/google/s2a-go v0.1.7 // indirect
github.com/google/uuid v1.6.0 // indirect
github.com/googleapis/enterprise-certificate-proxy v0.3.2 // indirect
github.com/googleapis/gax-go/v2 v2.12.4 // indirect
go.mod: set go version to 1.17 This is not a new requirement... I started using 1.17 features at some point in the past (as indicated in the CI tests). I just missed declaring that requirement in the go.mod file. With go1.17, the structure of the go.mod files changes a bit, but this shouldn't actually have any actual changes in the dependency tree.
2023-01-31 23:23:50 -05:00
github.com/jmespath/go-jmespath v0.4.0 // indirect
bump go version to 1.18 and update deps
2023-08-02 10:23:11 -05:00
github.com/kr/text v0.2.0 // indirect
update all dependencies to latest versions
2019-03-22 14:39:05 -05:00
github.com/nfnt/resize v0.0.0-20180221191011-83c6a9932646 // indirect
go.mod: update modules
2024-05-08 23:15:03 -05:00
github.com/prometheus/client_model v0.6.1 // indirect
github.com/prometheus/common v0.53.0 // indirect
github.com/prometheus/procfs v0.14.0 // indirect
go.mod: set go version to 1.17 This is not a new requirement... I started using 1.17 features at some point in the past (as indicated in the CI tests). I just missed declaring that requirement in the go.mod file. With go1.17, the structure of the go.mod files changes a bit, but this shouldn't actually have any actual changes in the dependency tree.
2023-01-31 23:23:50 -05:00
go.opencensus.io v0.24.0 // indirect
go.mod: update modules
2024-05-08 23:15:03 -05:00
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.51.0 // indirect
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.51.0 // indirect
go.opentelemetry.io/otel v1.26.0 // indirect
go.opentelemetry.io/otel/metric v1.26.0 // indirect
go.opentelemetry.io/otel/trace v1.26.0 // indirect
golang.org/x/crypto v0.23.0 // indirect
golang.org/x/net v0.25.0 // indirect
golang.org/x/oauth2 v0.20.0 // indirect
golang.org/x/sync v0.7.0 // indirect
golang.org/x/sys v0.20.0 // indirect
golang.org/x/text v0.15.0 // indirect
golang.org/x/time v0.5.0 // indirect
google.golang.org/api v0.178.0 // indirect
google.golang.org/genproto v0.0.0-20240506185236-b8a5c65736ae // indirect
google.golang.org/genproto/googleapis/api v0.0.0-20240506185236-b8a5c65736ae // indirect
google.golang.org/genproto/googleapis/rpc v0.0.0-20240506185236-b8a5c65736ae // indirect
google.golang.org/grpc v1.63.2 // indirect
google.golang.org/protobuf v1.34.1 // indirect
switch to use go module support versions of all dependencies remain the same, but now use `go mod` to manage them rather than govendor. This does result in a few extra files being checked in, since govendor would ignore non-build files and go mod does not.
2018-09-15 02:38:09 -05:00
)
Reference in a new issue Copy permalink