Update to Dapr 1.4 about dapr-workshop

[mthmulders]

I think they forgot to create the GitHub release for that 1.3.0 tag. The latest version, according to search.maven.org, is 1.3.0. That search can be a bit behind Central itself, so if search.maven.org says it, it's certainly in Central.

Should we verify that the Python 1.3.0 and the Java 1.3.0 releases are compatible with the 1.4.0 sidecars?

[mthmulders]

Ok, I've updated the documentation for Java SDK to 1.3.0.

I've updated the starting point (it has the version number in Maven dependency management).

The check is not necessary because the runtime (sidecars) is backward compatible.

I was hoping for this... :-) Good to know it is, in fact.

[wmeints]

Are we going to risk it and upgrade this before the workshop?

[wmeints]

Apparently, I'm already running on 1.4 on my machine :P So the python version works

[EdwinVW]

I'll upgrade the C# stuff a.s.a.p.

[EdwinVW]

I've updated all descriptions and the version table in the main README in 0276292 :

• For .NET, the latest SDK version is 1.4.0
• For Java, the latest SDK version is 1.2.0
• For Python the latest SDK version is 1.3.0

For Java, these is a 1.3.0 tag, but this is not the latest release. Can you double check @mthmulders ?

[EdwinVW]

Ok, I've updated the documentation for Java SDK to 1.3.0.
The check is not necessary because the runtime (sidecars) is backward compatible.

[EdwinVW]

I was hoping for this... :-) Good to know it is, in fact.

This is the case for the .NET SDK. My assumption was that this is also true for Java. But obviously an extra test (or scanning the release notes for breaking changes) to make sure it works, would not hurt (except that it takes time).

[mthmulders]

For Java, these is a 1.3.0 tag, but this is not the latest release. Can you double check @mthmulders ?

A little late to the party, but it now is: https://github.com/dapr/java-sdk/releases/tag/v1.3.0