[release] ChirpStack v4.11

v4.11.0

Improvements

Refactor (multi-region) de-duplication

This release refactors the uplink de-duplication, such that uplinks received by gateways in different region configurations (but with overlapping channels) are de-duplicated separately. After de-duplication and after resolving the device-session of the device, ChirpStack will only handle the de-duplicated uplink that is within the same region-configuration assigned to the device-session.

This makes it possible to create region configurations of which channels and gateway-coverage are overlapping. Before this release such scenario could result in constantly changing settings (through mac-commands) of the end-device or errors related to unknown channels.

This does include two integration changes:

  • Region information is no longer exposed through the rxInfo elements.
  • A new region_config_id field has been added to join and uplink events.

I have been focused on other areas of my service and am still running ChirpStack 4.7. Can I go directly to 4.11 or is it recommended to upgrade to 4.8, 4.9, etc. to get to 4.11?

While it is always good to “dry-run” an upgrade on a test environment (and to make backups), you should be able to upgrade from v4.7 to v4.11.0 directly. ChirpStack keeps track of the database migrations, and on start will apply what hasn’t applied yet (all database migrations are embedded inside the binary).

1 Like