This repository has been archived by the owner on Jul 12, 2023. It is now read-only.
v1.5.1
Changes since v1.5.0
Bugs
- Fix a bug with the sms anomalies emailer where it may fail after the first run.
Changes since v1.4.0
UI
- Add explanation for possible delta in token claim / publish rate due to iOS user-report behavior (#2309, @bschlaman)
Operations
- Add functionality for sending alert emails to realm contacts for SMS and code anomalies. This removes the server operator from the loop in alerting realms of potential issues with SMS error rates or code claim ratios. However, this does require configuration and setup. If you previously enabled twilio ignored codes, remove the
ignored_twilio_error_codes
definition from your Terraform. For detailed setup instructions, see https://github.com/google/exposure-notifications-verification-server/blob/main/docs/production.md#setup-system-emails. This introduces a new service,emailer
. When deploying, runterraform taint module.en.null_resource.build
to ensure the new service is built. The initial Terraform deployment may fail with errors about a missing metric. After you configure the emailer as noted above, update the Terraform configuration for module theen
anden-alerting
module and setenable_emailer = true
, then run Terraform a second time and it will succeed. If you restrict ingress traffic, also ensure add the revision annotation"run.googleapis.com/ingress" : "all"
to theemailer
service. (#2308, @sethvargo) - Add support for setting CC and BCC on all system-sent emails. To configure this, see the production guide for sending system emails. (#2320, @sethvargo)
- Only register metric descriptors that have not yet been registered. (#2311, @sethvargo)
SMS
- Allow user report to utilize a different "from" number for SMS sending. This can help reduce queuing and self report codes being blocked by a large bulk issue in a jurisdiction. (#2312, @mikehelmick)
- Fix an issue where the server might crash when a large number of codes were submitted to the SMS provider and the SMS provider rejects the request due to a queueing issue. (#2307, @sethvargo)
Dependencies
Added
- cloud.google.com/go/compute: v1.0.0
- cloud.google.com/go/iam: v0.1.0
Changed
- cloud.google.com/go/monitoring: v1.1.0 → v1.2.0
- cloud.google.com/go: v0.98.0 → v0.100.2
- github.com/Azure/azure-sdk-for-go: v60.0.0+incompatible → v61.2.0+incompatible
- github.com/Azure/go-autorest/autorest/adal: v0.9.17 → v0.9.18
- github.com/Azure/go-autorest/autorest/azure/auth: v0.5.9 → v0.5.11
- github.com/Azure/go-autorest/autorest/azure/cli: v0.4.4 → v0.4.5
- github.com/Azure/go-autorest/autorest: v0.11.22 → v0.11.24
- github.com/aws/aws-sdk-go: v1.42.20 → v1.42.35
- github.com/benbjohnson/clock: v1.1.0 → v1.3.0
- github.com/checkpoint-restore/go-criu/v5: v5.0.0 → v5.3.0
- github.com/chromedp/cdproto: d2673e9 → dcaca7e
- github.com/cilium/ebpf: v0.6.2 → v0.7.0
- github.com/cncf/xds/go: a8f9461 → cb28da3
- github.com/containerd/console: v1.0.2 → v1.0.3
- github.com/containerd/continuity: v0.2.1 → v0.2.2
- github.com/cyphar/filepath-securejoin: v0.2.2 → v0.2.3
- github.com/envoyproxy/go-control-plane: v0.10.1 → cf90f65
- github.com/envoyproxy/protoc-gen-validate: v0.6.2 → v0.1.0
- github.com/fsnotify/fsnotify: v1.4.9 → v1.5.1
- github.com/gin-gonic/gin: v1.7.4 → v1.7.7
- github.com/go-playground/validator/v10: v10.9.0 → v10.10.0
- github.com/go-sql-driver/mysql: v1.5.0 → v1.6.0
- github.com/godbus/dbus/v5: v5.0.4 → v5.0.6
- github.com/gofrs/uuid: v4.0.0+incompatible → v4.1.0+incompatible
- github.com/google/exposure-notifications-server: v1.3.0 → v1.5.0
- github.com/hashicorp/go-hclog: v1.0.0 → v1.1.0
- github.com/hashicorp/go-version: v1.3.0 → v1.4.0
- github.com/hashicorp/vault/api: v1.3.0 → v1.3.1
- github.com/joho/godotenv: v1.3.0 → v1.4.0
- github.com/mattn/go-ieproxy: v0.0.1 → v0.0.2
- github.com/mattn/go-sqlite3: v1.14.6 → v1.14.9
- github.com/microcosm-cc/bluemonday: v1.0.16 → v1.0.17
- github.com/moby/sys/mountinfo: v0.4.1 → v0.5.0
- github.com/nyaruka/phonenumbers: v1.0.73 → v1.0.74
- github.com/opencontainers/runc: v1.0.3 → v1.1.0
- github.com/opencontainers/selinux: v1.8.2 → v1.10.0
- github.com/seccomp/libseccomp-golang: v0.9.1 → 3879420
- github.com/sethvargo/go-retry: v0.1.0 → v0.2.2
- go.uber.org/goleak: 6911603 → v1.1.11
- go.uber.org/zap: v1.19.1 → v1.20.0
- golang.org/x/crypto: 5770296 → 5e0467b
- golang.org/x/net: 266e24b → 0dd24b2
- golang.org/x/sys: 97ca703 → da31bd3
- google.golang.org/api: v0.61.0 → v0.65.0
- google.golang.org/genproto: 3cb0678 → d2e6a12
- google.golang.org/grpc: v1.42.0 → v1.43.0