kyma-runtime-extension-samples icon indicating copy to clipboard operation
kyma-runtime-extension-samples copied to clipboard

Published 20 hours ago • verified publisher icon SAP-samples

Bump semver and dapr-client in /custom-component-dapr

Open dependabot[bot] opened this issue 2 years ago • 2 comments

Removes semver. It's no longer used after updating ancestor dependency dapr-client. These dependencies need to be updated together.

Removes semver

Updates dapr-client from 1.0.2 to 3.1.2

Release notes

Sourced from dapr-client's releases.

Release v3.1.2

What's Changed

The SDK v3.1.1's package-lock.json did not have the updated version (3.1.1), which can cause unexpected behavior. This new patch is to fix that.

Chores

Full Changelog: https://github.com/dapr/js-sdk/compare/v3.1.1...v3.1.2

Release v3.1.1

What's Changed

We are releasing a hotfix to handle issues with the crypto api implementation.

Fixes

Full Changelog: https://github.com/dapr/js-sdk/compare/v3.1.0...v3.1.1

Release v3.1.0

What's Changed

Features

Fixes

Chores

New Contributors

... (truncated)

Changelog

Sourced from dapr-client's changelog.

Changelog

3.x release

v3.0.0

Breaking Changes

General: Fix serialization of data in HTTP

There is a new serializer in place to automatically detect the Content-Type for the data when using the HTTP Protocol and serialize accordingly. Objects will be send as application/json, Cloud-Events as applications/cloudevents+json, Strings as text/plain, and others as application/octet-stream.

An example of this change can be seen when performing client.invoke with "hello world" as data. The new serializer will correctly return the string type, as opposed to the previous behavior of calling JSON.serialize and returning '"hello world"'.

PubSub: Changes to the subscribe callback for HTTP

The HTTP subscribe callback now returns data after parsing it correctly. Data is either extracted from the body's data field, or the data_base64 field. data_base64 is always expected to be a base64 encoded string, and will be decoded and parsed as JSON if possible. If it is not JSON, it will be returned as a string. If data is not found in either field, the entire body will be returned as-is.

2.x release

v2.0.1

Actors

To make development easier, Actors can now be called in 2 ways:

  1. By creating an actor through a helper method in the DaprClient class, removing the need of needing to know how a builder works.
const actor = await client.actor.create<DemoActorSayImpl>(DemoActorSayImpl);
const res = await actor.sayMulti(123, "123", { hello: "world 123" }, [1, 2, 3]);
  1. By utilizing the Actor builder, where we create a Proxy object that does this for us.
const builder = new ActorProxyBuilder<DemoActorSayImpl>(DemoActorSayImpl, client);
const actor = builder.build(ActorId.createRandomId());
const res = await actor.sayMulti(123, "123", { hello: "world 123" }, [1, 2, 3]);

Behind the hoods, method #1 will utilize method #2

v2.0.0

Version 2.0.0 brings a lot of changes to the Dapr JS SDK that were long due. Below an overview of the major contributions can be found, with a more detailed overview of the Breaking Changes under it.

  • Actor Support has been added
  • Actor Proxy has been added for Actor Access
  • The HTTP Connection is now being reused to reduce the CONNRESET errors when intensively using the JS SDK

... (truncated)

Commits
  • 960a10d chore(release): bump to v3.1.2 (#506)
  • 78f816a chore(release): bump version in package-lock.json (#504)
  • 0bf7020 chore: bump package version
  • 0b881c2 Fixed handling of backpressure in DaprChunkedStream (#503)
  • 553431f chore(release): prepare for v3.1.0 release (#501)
  • 1e3b6eb Added docs for crypto APIs (#500)
  • 5e42a79 feat(workflow): Add workflow management HTTP APIs (#485)
  • af71496 Crypto: Encrypt and Decrypt (#491)
  • 1114591 updating config API to use v1 endpoint (#496)
  • b1fb0c2 bug(ci): explicitly call pre-build while building for publish steps (#495)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.

dependabot[bot] avatar Jun 25 '23 19:06 dependabot[bot]

CLA assistant check
All committers have signed the CLA.

cla-assistant[bot] avatar Jun 25 '23 19:06 cla-assistant[bot]

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

cla-assistant[bot] avatar Jun 25 '23 19:06 cla-assistant[bot]