Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

General notes:

NOTE

  • Version numbers are formatted as x.y.z where x=major version, y=minor version and z=patch version

  • Regarding Blue/Green upgrades:

    • Blue/Green upgrades can be performed on environments running version a.b.c or newer.

    • ClearBlade only guarantees compatibility between one minor version and the next.

    • If an environment needs to be upgraded from one version to another in a Blue/Green fashion where the origin and target versions are separated by more than one minor version, then:

      • Multiple upgrade steps are required.

      • The steps must upgrade the environment to each of the minor versions between the origin and target versions.

      • Only one step per minor version is required.

      • Although a step can be used to upgrade to any patch version within a minor version, it is recommended that the latest patch version is chosen. This is because the latest patch version is likely to incorporate the most bug fixes.

      • For example, if upgrading from 9.36.2 to 9.38.0 either of these series of steps can be used:

        • 9.36.2 -> 9.37.2 -> 9.38.0

        • 9.36.2 -> 9.37.4 -> 9.38.0 (recommended)

9.38.3

Date:2024-11-22

Notes:

Platform:

  • Enhancement: Use caller name instead of lock name in lock metrics

  • Fix: Send error response on bucketset file create failures

  • Fix: Better version comparison algorithm for edge upgrades

9.38.2

Date:2024-11-15

Notes:

Platform:

  • Fix: Stop overwriting redirect responses from services with status codes in the 300s

  • Fix: Properly initialize node socket object to avoid push call on undefined object error

  • Fix: Add details to s3 files in bucketset list endpoint

  • Fix: Always set deployment name in sync status messages

  • Fix: Ensure async functions run asynchronously in v8

  • Fix: Better promise rejection handling in v8

  • Fix: Use proper parameter order for create_jwt in v8

  • Fix: Fire triggers on collection actions in v8

9.38.1

Date:2024-11-05

Notes:

Platform:

  • Fix: Only flush timer cache during init on leader node

  • Fix: Only add a node to the leader manager after a successful connection

  • Fix: Skip data upsert with no data in system upload collection handler to avoid panic

9.38.0

Date:2024-10-17

Notes:

...

  • Feature: Add log levels to code services

  • Feature: Add admin endpoint to reset database statistics

  • Feature: Add requireLibrary to v8

  • Enhancement: Allow filtering edges based on connectivity status

  • Enhancement: Remove system secrets

  • Enhancement: Add additional logging and auditing to service account session deletion

  • Enhancement: Ignore unregistered RPC messages

  • Enhancement: Migrate PubSub connections to MQTT connectors

  • Enhancement: Add prometheus metric for gRPC connections

  • Enhancement: Add prometheus metric for RPC execution times

  • Fix: Don't print periodic stat logs when executing subcommands

  • Fix: Add external broker connections back to prometheus metrics

Console:

  • Enhancement: Remove system secret from system settings page

  • Fix: Allow edge names to start with a number

9.37.5

Date:2024-11-05

Notes:

Platform:

  • Fix: Only flush timer cache during init on leader node

  • Fix: Only add a node to the leader manager after a successful connection

  • Fix: Skip data upsert with no data in system upload collection handler to avoid panic

9.37.4

Date:2024-10-17

Notes:

...