chore(deps): update all non-major regex dependencies #796
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.52.3
->1.60.0
0.20.0
->0.21.5
1.37.0
->1.45.0
1.14.0
->1.14.1
1.14.1
->1.14.4
3.5.1
->3.5.3
1.23.0
->1.23.2
4.17.1
->4.18.1
1.60.1
->1.61.0
0.2.112
->0.3.17
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
air-verse/air (air-verse/air)
v1.60.0
Compare Source
What's Changed
New Contributors
Full Changelog: air-verse/air@v1.52.3...v1.60.0
authzed/zed (authzed/zed)
v0.21.5
Compare Source
What's Changed
Full Changelog: authzed/zed@v0.21.4...v0.21.5
v0.21.4
Compare Source
What's Changed
Full Changelog: authzed/zed@v0.21.3...v0.21.4
v0.21.3
Compare Source
Fixing broken release process
What's Changed
Full Changelog: authzed/zed@v0.21.2...v0.21.3
v0.21.2
Compare Source
What's Changed
Full Changelog: authzed/zed@v0.21.1...v0.22.0
v0.21.1
Compare Source
What's Changed
Full Changelog: authzed/zed@v0.21.0...v0.21.1
v0.21.0
Compare Source
What's Changed
New Contributors
Full Changelog: authzed/zed@v0.20.0...v0.21.0
bufbuild/buf (bufbuild/buf)
v1.45.0
Compare Source
buf registry module info --format=json
to adddefault_label_name
, which provides the nameof the default label of a module.
v1.44.0
Compare Source
PROTOVALIDATE
lint rule to check example field options. Examples will be checked thatthey satisfy the field constraints, and are only present if constraints are present.
PROTOVALIDATE
lint rule to check predefined rules. Predefined rules will be checkedthat they compile.
.wasm
file extension to specify a path to a Wasm plugin.v1.43.0
Compare Source
buf beta lsp
.v1.42.0
Compare Source
our launch blog post
for more details!
buf dep graph --format
flag that defaults todot
, and adds the optionjson
, to printthe dependency graph in JSON format.
buf format
where trailing comments on commas in message literals were not properlypropagated to the formatted proto, empty message literals were not properly indented, and
compound strings in options added an extra newline before trailing commas.
v1.41.0
Compare Source
buf curl
.v1.40.1
Compare Source
buf lint
where comment ignores in the shape of// buf:lint:ignore <RULE_ID> <extra comment>
were not recognized due to the extra comment.
v1.40.0
Compare Source
buf config ls-{breaking,lint}-rules
. Default rules are those rules which are run if no lintor breaking rules are explicitly configured in your
buf.yaml
.DEFAULT
lint rule category toSTANDARD
. With the concept of default rules being introduced,having a category named
DEFAULT
is confusing, as while it happens that all the rules in theDEFAULT
lint category are also default rules, the name has become overloaded. As with all
buf
changes, thischange is backwards-compatible: the
DEFAULT
lint category continues to work, and always will. Werecommend changing to
STANDARD
, however.v1.39.0
Compare Source
includes
key to module configurations in v2buf.yaml
, accepting a list of directories.includes
is specified, a proto file is considered in the module only if it is in one of thedirectories specified.
includes
andexcludes
keys are specified for a module, a proto file is consideredpart of this module if it is contained in any of the include paths and not in any of the exclude
paths.
buf.yaml
to have the same directory path.v1.38.0
Compare Source
--http3
flag tobuf curl
which forcesbuf curl
to use HTTP/3 as the transport.a path to a module, but contained directories with modules, and the modules would not build.
buf.lock
files whenbuf dep update
does not find new dependenciesto update and there is no existing
buf.lock
.buf push
to push the license file or doc file (e.g.README.md
,LICENSE
) in thesame directory as
buf.yaml
if a module does not have a license file or doc file in themodule's directory.
--path
flag for lint and breaking rules to avoid resolving all fileswithin a module. This change can result in a performance improvement for large workspaces.
dapr/cli (dapr/cli)
v1.14.1
: Dapr CLI v1.14.1Compare Source
dapr/dapr (dapr/dapr)
v1.14.4
: Dapr Runtime v1.14.4Compare Source
Dapr 1.14.4
This update includes bug fixes:
Fixes being able to upgrade Dapr v1.14.x to v1.14.3 without manual intervention
Problem
When upgrading from Dapr versions
v1.14.0
,v1.14.1
, orv1.14.2
tov1.14.3
, the upgrade would fail with the following error.The workaround for the user is to Delete the Scheduler StatefulSet before re-running the upgrade with the new storage size.
The StorageClass must support volume expansion for this to work.
Impact
Users were unable to upgrade Dapr to
v1.14.3
without manual intervention, breaking automated upgrades.Root cause
In Dapr
v1.14.3
, thedapr-scheduler-server
StatefulSet changed the default persistent volume request size from1Gi
to16Gi
.Kubernetes prevents updating this request field, resulting in this the above error.
Solution
This field has been reverted to the previous
1Gi
request size.Users who wish to increase the volume size must follow the manual steps described in the documentation.
Fixes daprd not being able to connect to placement on k8s
Problem
When running dapr in high availability mode on Kubernetes, daprd would not be able to connect to the placement service after failure and re-election of a Placement leader.
Impact
The dapr sidecar would not be able to connect to the placement service, and would not be able to receive the actor placement tables.
Root cause
The connection to the failed placement leader was being properly closed, but not set to nil, so it was being reused.
Solution
The additional check was removed.
v1.14.3
: Dapr Runtime v1.14.3 [RECALLED]Compare Source
Dapr 1.14.3
v1.14.0
,v1.14.1
, orv1.14.2
tov1.14.3
, the upgrade fails with the following error:The workaround for the user is to Delete the Scheduler StatefulSet before re-running the upgrade with the new storage size, but we recommend skipping this version and upgrading to
v1.14.4
or later instead.This update includes bug fixes:
Fix AWS Secrets Manager and Parameter Store components when working with more granular IAM permissions
Problem
When using AWS Secrets Manager and Parameter Store daprd would fail on initialisation if the IAM policy would only allow access for certain secrets.
Impact
Dapr wouldn't be able to start if the IAM policy would only allow access to certain secrets.
Root cause
On initialisation daprd would try to verify access to the AWS Secrets Manager and Parameter Store services by trying to read a dummy secret which would fail if the IAM policy in place would only allow access to certain secrets.
Solution
The additional check was removed.
Fix Scheduler embedded ETCD database running out of memory
Problem
Creating a reasonable number of Jobs or Actor Reminders (also through workflows) with the Scheduler, would case the embedded Scheduler to run out of memory.
Impact
The Jobs, Actor Reminders, and Workflow APIs would become unavailable.
Root cause
The default storage size of the embedded ETCD database was too small, as well as the purging of deleted data was not sufficiently aggressive enough.
Solution
Increase the default storage size of the embedded ETCD database from 2Gi to 16Gi, increase the frequency of purging of deleted data.
More options are now exposed on the Scheduler to tune these values further.
Fix the Job HTTP Trigger Request body base64 encoding values
Problem
When handling a Job trigger in a HTTP application, the value content of the request body could be base64 encoded, causing application serialization errors.
Impact
The Job trigger would not be processed by the application correctly.
Root cause
The Job trigger was erroneously encoding the request body value content when sending the request to the applicaiton.
Solution
daprd now sends the request body value content as a standard JSON string.
Change the HTTP Job API request body data field to accept JSON strings
Problem
The HTTP Job API request body data field previously accepted fully qualified protobuf messages.
Impact
The HTTP API was less approachable for users who wanted to test and develop with the HTTP API, often times using curl or Postman etc.
Root cause
The HTTP Job API used the same request schema as the gRPC API.
Solution
The HTTP Job API now accepts JSON strings for the request body data field.
Add securityContext/runAsGroup and securityContext/runAsUser as sidecar injector options
Problem
daprd sidecar is missing the
securityContext/runAsGroup
and/orsecurityContext/runAsUser
settings.Impact
daprd sidecar was not passing security checks by some policy enforcement solutions and could not run.
Root cause
Missing the ability to set the
securityContext/runAsGroup
and/orsecurityContext/runAsUser
settings.Solution
Added the
dapr_sidecar_injector.sidecarRunAsUser
and/ordapr_sidecar_injector.sidecarRunAsGroup
helm chart settings.v1.14.2
: Dapr Runtime v1.14.2Compare Source
Dapr 1.14.2
Fix Memory Leak when running Workflows
Problem
When using workflows, daprd would increase in memory consumption indefinitely, eventually causing daprd to crash from a Out Of Memory Kill (OOM Kill),
Impact
Daprd would consume extra resources from the host, and periodically become unavailable and disrupt running tasks.
Root cause
The actor runtime in Daprd was not releasing memory of workflow actors, and the associated workflow state (history, inbox, etc.).
Solution
The actor runtime now correctly releases the workflow state once that workflow has reached a terminal state.
Fix nil map error on Placement Service state restore from an older version
Problem
When a Placement Service instance using on disk logs was upgraded to 1.14 in some cases we would get a nil map error and the instance would not start.
Impact
Dapr Placement Service instance would not start.
Root cause
Restoring the old format would override the state saved in Raft with a struct that wasn't properly initialised.
Solution
Initialize the struct properly when restoring the old format.
Fix non-URL encoded Kafka headers causing event delivery to fail over HTTP
Problem
When Kafka headers are present that are not URL encoded, the event delivery to the app will fail with a retriable error.
Impact
Messages cannot be delivered to the app.
Root cause
Lack of URL encoding on header values from Kafka.
Solution
Add URL encoding to Kafka headers.
Fix AWS Secret Manager and Parameter Store initialization
Problem
If users had IAM policies in place that only allowed access to specific secrets, the initialization of the AWS secret manager and parameter store components would fail.
Impact
Components could not be initialized.
Root cause
There was a redundant check in initialization that tried to read a random secret which caused the init to fail if a policy was present to only allow reading specific secrets.
Solution
The redundant check was removed.
Fix Kafka Avro validation for null values
Problem
When publishing a message containing a null byte array with Kafka and Avro validation enabled, the message would be rejected when it shouldn't be.
Impact
A message could not be sent.
Root cause
There was a missing validation logic for null byte arrays that would allow the message to continue processing.
Solution
The missing validation logic was added.
Fix Kafka edge case of lost messages upon process termination
Problem
In certain cases, Dapr would drop a Kafka message when it should have been retried if the
daprd
process is abruptly terminated.Impact
A message would not be retried upon failure.
Root cause
Message processing logic moved on to process the next message instead of exiting when the session context was done.
Solution
The code was changed to handle session context exiting prior to processing the next message.
Fix Outbox not sending messages to the user topic
Problem
If outbox was being used and a publisher didn't have an app channel open or the subscriber didn't have access to the transactional state store, then outbox messages would not be published.
Impact
Outbox messages could not be sent.
Root cause
Faulty logic that required Dapr to have an app channel in order to subscribe to the internal topics.
Solution
Enable Dapr to subscribe to internal topics without needing an app channel.
dart-lang/sdk (dart)
v3.5.3
Compare Source
issue resulting in a missing tab bar when DevTools is embedded in
IntelliJ and Android Studio (issue#56607).
DevTools is opened instead of only the first time (issue#56607).
embedded in IntelliJ and Android Studio (issue#56607).
v3.5.2
Compare Source
ZLibDecoder
would incorrectly attempt to decompress datapast the end of the zlib footer (issue #56481).
dart
fromPATH
could result in some commands notworking as expected (issues #56080, #56306, #56499).
setContextRoots
requests orbeing provided incorrect context roots in multi-package workspaces (issue
#56475).
golang-migrate/migrate (golang-migrate/migrate)
v4.18.1
Compare Source
Changes
Full Changelog: golang-migrate/migrate@v4.18.0...v4.18.1
v4.18.0
Compare Source
What's Changed
rand.Seed()
in testing.docker by @joschi in https://github.com/golang-migrate/migrate/pull/1149A special thanks to @joschi fixing tests and builds!
New Contributors
Full Changelog: golang-migrate/migrate@v4.17.1...v4.17.2
golangci/golangci-lint (golangci/golangci-lint)
v1.61.0
Compare Source
junit-xml-extended
formatdupword
: from 0.0.14 to 0.1.1fatcontext
: from 0.4.0 to 0.5.2gci
: from 0.13.4 to 0.13.5 (new optionno-lex-order
)go-ruleguard
: from 0.4.2 to0fe6f58
(fix panic with custom linters)godot
: from 1.4.16 to 1.4.17gomodguard
: from 1.3.3 to 1.3.5gosec
: disable temporarilyG407
gosec
: fromab3f6c1
to 2.21.2 (partially fixG115
)intrange
: from 0.1.2 to 0.2.0nolintlint
: remove the empty line in the directive replacementtypecheck
v1.60.3
Compare Source
gosec
: from81cda2f
toab3f6c1
(fixG115
false positives)v1.60.2
Compare Source
gofmt
: update to HEAD (go1.22)gofumpt
: from 0.6.0 to 0.7.0gosec
: fix G602 analyzergosec
: from5f0084e
to81cda2f
(addsG115
,G405
,G406
,G506
,G507
)staticcheck
: from 0.5.0 to 0.5.1staticcheck
: propagate Go versionwrapcheck
: from 2.8.3 to 2.9.0exportloopref
: deprecationsuperfly/flyctl (superfly/flyctl)
v0.3.17
Compare Source
Changelog
59f3672
Bump the aws-sdk group with 3 updates (#3988)767fbc4
Bump the golangx group with 6 updates (#3984)1dfbe88
Bump github.com/superfly/fly-go from 0.1.31 to 0.1.32 (#3985)236bef5
Bump the aws-sdk group across 1 directory with 3 updates (#3986)v0.3.16
Compare Source
Changelog
d59a12f
Fix that metadata submission would fail for nil entries (#3987)5355d4e
fix: fix slice init length (#3982)v0.3.15
Compare Source
Changelog
8453296
Allow releasing static egress IPs from machines (#3978)v0.3.14
Compare Source
Changelog
19481df
Bump google.golang.org/grpc from 1.67.0 to 1.67.1 (#3974)957c545
Bump github.com/superfly/fly-go from 0.1.29 to 0.1.30 (#3975)v0.3.13
Compare Source
Changelog
ffc222f
machines-only flag is gone since nomad is not a thing (#3972)1e64062
Bump the aws-sdk group with 3 updates (#3971)a8debdf
Run Rails thruster on port 8080. (#3969)v0.3.12
Compare Source
Changelog
925283c
Bump the aws-sdk group with 3 updates (#3967)v0.3.11
Compare Source
What's Changed
fly app restart
only restarts started machines by @dangra in https://github.com/superfly/flyctl/pull/3970Full Changelog: superfly/flyctl@v0.3.10...v0.3.11
v0.3.10
Compare Source
Changelog
fb8153e
half the default max concurrent value to 8 (#3961)v0.3.8
Compare Source
Changelog
db4d0d7
Add flyctl commands for static egress IPs (#3934)af22df9
generate rails secrets inline rather than shelling out (#3958)v0.3.7
Compare Source
Changelog
e6cdd34
Ensure builders set without buildpacks fall back to Fly builders (#3957)d156d43
Bump github.com/docker/docker from 27.3.0+incompatible to 27.3.1+incompatible (#3956)93e724c
Add library to pull config from remote container images (#3905)f9a14b8
fix: fly volume fork --require-unique-zone should be default (#3955)f086b4f
Bump google.golang.org/grpc from 1.66.2 to 1.67.0 (#3951)615681b
return error message for machines list failure (#3954)e81e0e2
Bump github.com/docker/docker from 27.2.1+incompatible to 27.3.0+incompatible (#3952)v0.3.6
Compare Source
Changelog
9ecc149
test: add logging around testDeployNodeApp* tests (#3945)v0.3.5
Compare Source
Changelog
c4e44d4
Obey alternate registry settings for Docker auth (#3947)b4d50e8
Bump github.com/prometheus/client_golang from 1.20.3 to 1.20.4 (#3946)v0.3.4
Compare Source
Changelog
76d027c
Add flyctl commands for managing secrets that are kms keys (#3901)v0.3.2
Compare Source
Changelog
3eb4638
Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.54.0 to 0.55.0 in the tracing group (#3940)8ebae56
Bump google.golang.org/grpc from 1.66.1 to 1.66.2 (#3941)v0.3.1
Compare Source
Changelog
920d4db
Bump rack from 2.2.6.4 to 2.2.8.1 in /example-buildpack (#3938)da0c2d5
test: run slow deploy-related tests in parallel (#3935)8097b5a
Bump the tracing group with 5 updates (#3936)v0.3.0
Compare Source
What's Changed
Full Changelog: superfly/flyctl@v0.2.127...v0.3.0
v0.2.127
Compare Source
Changelog
4338c9a
scale count/show: exclude Machines on unavailable hosts (#3923)4721e0a
Bump github.com/getsentry/sentry-go from 0.28.1 to 0.29.0 (#3928)v0.2.126
Compare Source
Changelog
c44f26f
Default to offering Redis and Tigris for Phoenix apps (#3915)0c7b86c
Fix typo Update README (#3921)1f9f42f
Bump the golangx group with 6 updates (#3919)c015374
Bump github.com/prometheus/client_golang from 1.20.2 to 1.20.3 (#3920)e5bc56f
Write and clean up some tests around deploy/ package (#3918)v0.2.125
Compare Source
Changelog
19c7e64
Bump github.com/mattn/go-zglob from 0.0.5 to 0.0.6 (#3913)08fc0e8
Bump github.com/superfly/fly-go from 0.1.27 to 0.1.28 (#3912)1d7dd13
Bump github.com/mattn/go-zglob from 0.0.4 to 0.0.5 (#3911)v0.2.124
Compare Source
Changelog
790bb3b
add support for increment/decrement values infly scale count
(#3891)53a4387
Django scanner improvements (#3894)42e15e0
Bump slackapi/slack-github-action from 1.26.0 to 1.27.0 (#3908)343f703
Bump google.golang.org/grpc from 1.65.0 to 1.66.0 (#3909)4dc3ff9
Bump github.com/prometheus/client_golang from 1.20.1 to 1.20.2 (#3910)74a9fb4
Generates a dedicated token for synthetics (#3898)fd26f35
Improve error messages for failed deployments (#3856)v0.2.123
Compare Source
Changelog
1d007f8
add fly scale count --env (#3895)5f59d3a
Ask launchdarkly whether to use Depot as our default builder (#3900)44f22a3
Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.53.0 to 0.54.0 in the tracing group (#3903)c00fb27
Add condition to check nuxt on deps for detecting nuxt apps (#3868)v0.2.122
Compare Source
Changelog
a239452
refresh info about unattached vols each update retry (#3889)2eff0a2
Bump github.com/pelletier/go-toml/v2 from 2.2.2 to 2.2.3 (#3893)551d357
Bump the tracing group across 1 directory with 5 updates (#3897)db0cf1d
Fix panic when cloning a standby machine (#3896)v0.2.121
Compare Source
Changelog
307adcc
Scan the composer.json file for php version (#3873)65361c5
Bump github.com/superfly/fly-go from 0.1.26 to 0.1.27 (#3888)b0ce2a2
add FLY_STANDBY_FOR environment variable to standby machine (#3800)3382f71
fix: don't create machines in parallel (#3876)v0.2.120
Compare Source
Changelog
f023289
Bump github.com/miekg/dns from 1.1.61 to 1.1.62 (#3855)v0.2.119
Compare Source
Changelog
ec54ad9
correctly fix builderScopeString being "" (#3881)5fed40b
fix default value for depot-scope (#3880)ddf6ed1
Bump github.com/prometheus/client_golang from 1.19.1 to 1.20.1 (#3878)v0.2.118
Compare Source
Changelog
a7a30da
ci: bye macos-11 (#3877)12802c5
allow specifying builder scope for a single app or an org (#3869)v0.2.117
Compare Source
Changelog
7817ccc
fix: m.Config could be nil (#3848)34699b2
test: TestAppsV2Example was broken (#3874)v0.2.116
Compare Source
Changelog
a30f319
Deprecatefly auth token
command (#3872)v0.2.115
Compare Source
Changelog
885dd16
test: make Postgres tests more stable (#3857)0ee4071
Enable Tigris support for Laravel apps (#3866)fe8ed25
Support for scanners to add custom key name to replace an extension's secret key name (#3851)v0.2.114
Compare Source
Changelog
de9e822
Inventing deploy manifest (#3769)32dd7e5
show proper count of machines to be deleted when using fly machines destroy --force --image (#3861)Configuration
📅 Schedule: Branch creation - "* 18-21 * * 5" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.