Release Kalix JavaScript SDK 1.0.6

[efgpinto]

Prepare

• [x] Make sure all important PRs have been merged
• [x] Check that the latest build successfully finished
• [x] Make sure a version of the proxy that supports the protocol version the SDK expects has been deployed to production

You can see the proxy version on prod on grafana or using various other methods.

Cutting the release

• [x] Edit the draft release notes and publish with the appropriate tag.
  • CircleCI will automatically publish the @kalix-io/kalix-javascript-sdk package to the npm registry based on the tag
  • CI will update the docs/kalix-current branch

Check availability

• [x] Check that docs/kalix-current has been updated
• [x] Check the release in the npm registry

Fix and publish docs

• [ ] If relevant, update the supported version in the main docs (affects Supported Versions)
• [x] Add an item to the Release Notes in the documentation
• [ ] Release the Kalix documentation to get the SDK docs updates published. After running the commands in the previous link the release is automated.

Update to the latest version

• [x] Run samples/bin/update.sh to update the samples to the latest released versions.

Check docs update

• [ ] After quite a while TechHub shows updated docs (see the timestamp on the bottom of the page)

Announcements

• [x] Announce in the forum
  • tag with Kalix, releases and announcement
• [x] Inform Lightbend marketing and engineering if it's a noteworthy release
• [x] Close this issue

[efgpinto]

Supersedes #431

[efgpinto]

For the record, this failed when publishing the macos native image here.

This is due to the curl version used not supporting the --fail-with-body. I've pushed the image to cloudsmith manually, so ci pipeline is completed.

Will follow up with version bump for macos image being used.