Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update all non-major regex dependencies #796

Merged
merged 2 commits into from
Oct 9, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 23, 2024

This PR contains the following updates:

Package Update Change
air-verse/air minor 1.52.3 -> 1.60.0
authzed/zed minor 0.20.0 -> 0.21.5
bufbuild/buf minor 1.37.0 -> 1.45.0
dapr/cli patch 1.14.0 -> 1.14.1
dapr/dapr patch 1.14.1 -> 1.14.4
dart (source) patch 3.5.1 -> 3.5.3
golang patch 1.23.0 -> 1.23.2
golang-migrate/migrate minor 4.17.1 -> 4.18.1
golangci/golangci-lint minor 1.60.1 -> 1.61.0
superfly/flyctl minor 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

  • Update buf registry module info --format=json to add default_label_name, which provides the name
    of the default label of a module.

v1.44.0

Compare Source

  • Update the PROTOVALIDATE lint rule to check example field options. Examples will be checked that
    they satisfy the field constraints, and are only present if constraints are present.
  • Update the PROTOVALIDATE lint rule to check predefined rules. Predefined rules will be checked
    that they compile.
  • Add support for a WebAssembly (Wasm) runtime for custom lint and breaking changes plugins. Use the
    .wasm file extension to specify a path to a Wasm plugin.

v1.43.0

Compare Source

  • Add new experimental LSP support under buf beta lsp.

v1.42.0

Compare Source

  • Add support for custom lint and breaking change plugins. See
    our launch blog post
    for more details!
  • Add buf dep graph --format flag that defaults to dot, and adds the option json, to print
    the dependency graph in JSON format.
  • Fix bugs in buf format where trailing comments on commas in message literals were not properly
    propagated 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

  • Add HTTP/3 support for gRPC with buf curl.
  • Fix issue where errors from protoc plugins may be overwritten when executing plugins in parallel.

v1.40.1

Compare Source

  • Fix issue with 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

  • Add concept of a default lint or breaking rule, which is printed out as a property when running
    buf config ls-{breaking,lint}-rules. Default rules are those rules which are run if no lint
    or breaking rules are explicitly configured in your buf.yaml.
  • Rename DEFAULT lint rule category to STANDARD. With the concept of default rules being introduced,
    having a category named DEFAULT is confusing, as while it happens that all the rules in the DEFAULT
    lint category are also default rules, the name has become overloaded. As with all buf changes, this
    change is backwards-compatible: the DEFAULT lint category continues to work, and always will. We
    recommend changing to STANDARD, however.

v1.39.0

Compare Source

  • Fix git input handling of relative HEAD refs without branch names.
  • Add includes key to module configurations in v2 buf.yaml, accepting a list of directories.
    • If includes is specified, a proto file is considered in the module only if it is in one of the
      directories specified.
    • If both includes and excludes keys are specified for a module, a proto file is considered
      part of this module if it is contained in any of the include paths and not in any of the exclude
      paths.
  • Allow multiple module configurations in the same v2 buf.yaml to have the same directory path.

v1.38.0

Compare Source

  • Add --http3 flag to buf curl which forces buf curl to use HTTP/3 as the transport.
  • Fix issue with directory inputs for v2 workspaces where the specified directory was not itself
    a path to a module, but contained directories with modules, and the modules would not build.
  • Stop creating empty buf.lock files when buf dep update does not find new dependencies
    to update and there is no existing buf.lock.
  • Update buf push to push the license file or doc file (e.g. README.md, LICENSE) in the
    same directory as buf.yaml if a module does not have a license file or doc file in the
    module's directory.
  • Fix constraints of --path flag for lint and breaking rules to avoid resolving all files
    within a module. This change can result in a performance improvement for large workspaces.
dapr/cli (dapr/cli)

v1.14.1: Dapr CLI v1.14.1

Compare Source

dapr/dapr (dapr/dapr)

v1.14.4: Dapr Runtime v1.14.4

Compare 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, or v1.14.2 to v1.14.3, the upgrade would fail with the following error.

Error: UPGRADE FAILED: cannot patch "dapr-scheduler-server" with kind StatefulSet: StatefulSet.apps "dapr-scheduler-server" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'ordinals', 'template', 'updateStrategy', 'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden

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, the dapr-scheduler-server StatefulSet changed the default persistent volume request size from 1Gi to 16Gi.
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

⚠️ When upgrading from Dapr versions v1.14.0, v1.14.1, or v1.14.2 to v1.14.3, the upgrade fails with the following error:

Error: UPGRADE FAILED: cannot patch "dapr-scheduler-server" with kind StatefulSet: StatefulSet.apps "dapr-scheduler-server" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'ordinals', 'template', 'updateStrategy', 'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden

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/or securityContext/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/or securityContext/runAsUser settings.

Solution

Added the dapr_sidecar_injector.sidecarRunAsUser and/or dapr_sidecar_injector.sidecarRunAsGroup helm chart settings.

v1.14.2: Dapr Runtime v1.14.2

Compare 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

  • Fixes an issue with the DevTools Memory tool causing OOMs. and an
    issue resulting in a missing tab bar when DevTools is embedded in
    IntelliJ and Android Studio (issue#​56607).
  • Fixes an issue with the DevTools release notes showing each time
    DevTools is opened instead of only the first time (issue#​56607).
  • Fixes an issue resulting in a missing tab bar when DevTools is
    embedded in IntelliJ and Android Studio (issue#​56607).

v3.5.2

Compare Source

  • Fixes a bug where ZLibDecoder would incorrectly attempt to decompress data
    past the end of the zlib footer (issue #​56481).
  • Fixes issue where running dart from PATH could result in some commands not
    working as expected (issues #​56080, #​56306, #​56499).
  • Fixes analysis server plugins not receiving setContextRoots requests or
    being provided incorrect context roots in multi-package workspaces (issue
    #​56475).
golang-migrate/migrate (golang-migrate/migrate)

v4.18.1

Compare Source

Changes
  • Update dktest from v0.4.2 to v0.4.3

Full Changelog: golang-migrate/migrate@v4.18.0...v4.18.1

v4.18.0

Compare Source

What's Changed

A 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

  1. Enhancements
    • Add junit-xml-extended format
    • Exclude Swagger Codegen files by default
  2. Updated linters
    • dupword: from 0.0.14 to 0.1.1
    • fatcontext: from 0.4.0 to 0.5.2
    • gci: from 0.13.4 to 0.13.5 (new option no-lex-order)
    • go-ruleguard: from 0.4.2 to 0fe6f58 (fix panic with custom linters)
    • godot: from 1.4.16 to 1.4.17
    • gomodguard: from 1.3.3 to 1.3.5
    • gosec: disable temporarily G407
    • gosec: from ab3f6c1 to 2.21.2 (partially fix G115)
    • intrange: from 0.1.2 to 0.2.0
    • nolintlint: remove the empty line in the directive replacement
  3. Misc.
    • Improve runtime version parsing
  4. Documentation
    • Add additional info about typecheck

v1.60.3

Compare Source

  1. Updated linters
  2. Misc.
    • Check that the Go version use to build is greater or equals to the Go version of the project

v1.60.2

Compare Source

  1. Updated linters
  • gofmt: update to HEAD (go1.22)
  • gofumpt: from 0.6.0 to 0.7.0
  • gosec: fix G602 analyzer
  • gosec: from 5f0084e to 81cda2f (adds G115, G405, G406, G506, G507)
  • staticcheck: from 0.5.0 to 0.5.1
  • staticcheck: propagate Go version
  • wrapcheck: from 2.8.3 to 2.9.0
  • ⚠️ exportloopref: deprecation
superfly/flyctl (superfly/flyctl)

v0.3.17

Compare Source

Changelog

v0.3.16

Compare Source

Changelog

v0.3.15

Compare Source

Changelog

v0.3.14

Compare Source

Changelog

v0.3.13

Compare Source

Changelog

v0.3.12

Compare Source

Changelog

v0.3.11

Compare Source

What's Changed

Full Changelog: superfly/flyctl@v0.3.10...v0.3.11

v0.3.10

Compare Source

Changelog

v0.3.8

Compare Source

Changelog

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

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

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

v0.2.125

Compare Source

Changelog

v0.2.124

Compare Source

Changelog

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

v0.2.121

Compare Source

Changelog

v0.2.120

Compare Source

Changelog

v0.2.119

Compare Source

Changelog

v0.2.118

Compare Source

Changelog

v0.2.117

Compare Source

Changelog

v0.2.116

Compare Source

Changelog

v0.2.115

Compare Source

Changelog

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner August 23, 2024 19:12
@renovate renovate bot added the deps label Aug 23, 2024
@renovate renovate bot requested review from FoseFx and Paul-B98 and removed request for a team August 23, 2024 19:12
@renovate renovate bot force-pushed the renovate/all-non-major-regex-dependencies branch 8 times, most recently from 4f7b8f3 to 87eeebd Compare August 29, 2024 22:31
@renovate renovate bot force-pushed the renovate/all-non-major-regex-dependencies branch 9 times, most recently from 3103228 to 072f6a5 Compare September 9, 2024 20:28
@renovate renovate bot force-pushed the renovate/all-non-major-regex-dependencies branch 8 times, most recently from e60e8af to bc0970b Compare September 11, 2024 16:55
@renovate renovate bot force-pushed the renovate/all-non-major-regex-dependencies branch 7 times, most recently from ea2bee1 to 18693d7 Compare September 26, 2024 19:18
@renovate renovate bot force-pushed the renovate/all-non-major-regex-dependencies branch 8 times, most recently from 7d506d7 to b680236 Compare October 3, 2024 19:31
@renovate renovate bot force-pushed the renovate/all-non-major-regex-dependencies branch 8 times, most recently from 2a73269 to 8fae256 Compare October 8, 2024 21:51
@renovate renovate bot force-pushed the renovate/all-non-major-regex-dependencies branch from 8fae256 to 5e76195 Compare October 9, 2024 08:27
@FoseFx FoseFx merged commit 6cac7ec into main Oct 9, 2024
39 checks passed
Copy link
Contributor Author

renovate bot commented Oct 9, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@FoseFx FoseFx deleted the renovate/all-non-major-regex-dependencies branch October 9, 2024 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant