Update CHANGELOG for Mender Client 6.0.x

[mender-test-bot]

Mender Client 6.0.x

Repository	Version
mender	5.1.x
mender-connect	3.0.x
monitor-client	1.5.x
mender-flash	1.1.x
mender-configure-module	1.1.x
mender-binary-delta	1.5.x
mender-container-modules	1.0.x

mender 5.1.x (2026-05-28)

5.1.x - 2026-05-28

Bug fixes

• Don't retry status update on 413
  (ME-616) (e13437d)

• Handle first timestamp in deployment logs more carefully
  (MEN-9427) (68ab41e)

  Depending on the system and build configuration, the timestamps
  in logs can use lower (likely) or higher (unlikely) time
  resolution than expected (nanoseconds). So in case of a
  deployment failure with corrupted logs, when using the first
  timestamp as a replacement in the extra (THE ORIGINAL LOGS CONTAINED INVALID ENTRIES) log entry, care must be taken to make
  sure the extra log entry still has a valid timestamp and that the
  result is valid JSON.

• Sort inventory generator scripts before running them
  (MEN-9635) (a5fcec1)

  So that the results are consistent and don't depend on directory
  iteration ordering.

• Fail when device tier is invalid
  (ME-636) (590282f)

  DeviceTier is one of the configuration options but it is critical
  for how device is recognized by the server. When we will fail
  parsing it out of the configuration we should fail instead to
  switching to the standard device tier.

• Ensure limited permissions of mender-inventory-geo cache files
  (MEN-9752) (64584e2)

  The /tmp/mender/inventory-geo cache file can potentially contain
  sensitive data and there's no reason for it to have 644
  permissions.

  By using umask 077 we can easily ensure that any files created
  by the script are only user/owner-accessible.

Features

• Large deployment logs are now trimmed to be accepted by the server
  (MEN-9415) (d870064)

  Deployment logs larger than 1 MiB are rejected by the
  server which leads to two issues:

  • excessive bandwith consumption when uploading such large logs
    only to be thrown away, and

  • no deployment logs for particular device and particular failed
    deployment available at the server at all.

  To prevent this, the client now trims large deployment logs and
  only sends the biggest possible part of the logs from their end.

mender-connect 3.0.x (2026-02-27)

No changelog entries found.

monitor-client 1.5.x (2026-02-23)

No changelog entries found.

mender-flash 1.1.x (2026-02-27)

No changelog entries found.

mender-configure-module 1.1.x (2026-05-28)

No changelog entries found.

mender-binary-delta 1.5.x (2026-05-28)

No changelog entries found.

mender-container-modules 1.0.x (2026-05-05)

1.0.x - 2026-05-05

Bug fixes

• Cd into manifest dir beforing listing running containers
  (MEN-9641) (0aa83f8)

  Fix an issue where docker-compose v1 can't find manifest files for a
  composition because we don't cd into the manifest directory.

[mender-test-bot]

@mender-test-bot, start a full client pipeline with:

• mentioning me and start client pipeline

---

my commands and options

You can prevent me from automatically starting CI pipelines:

• if your pull request title starts with "[NoCI] ..."

You can trigger a client pipeline on multiple prs with:

• mentioning me and start client pipeline --pr mender/127 --pr mender-connect/255

You can trigger a client pipeline for a specific Mender Client release with:

• mentioning me and start client pipeline --release 6.0.x (can be given multiple times)
• by default, a pipeline is triggered for each supported release the component is a part of

You can trigger GitHub->GitLab branch sync with:

• mentioning me and sync

You can print PR statistics for a repository with:

• mentioning me and print fast pr stats (Team stats only)
• mentioning me and print full pr stats (Detailed report)
• options: --repo <repo>, --team <name>, --all-repos, --exclude-drafts, --exclude-user <user>
• mentioning me and print full pr stats --repo mender --all-repos --exclude-drafts

You can cherry pick to a given branch or branches with:

• mentioning me and:

 cherry-pick to:
 * 1.0.x
 * 2.0.x