chore(deps): update dependency mendersoftware/mender-artifact to v4.4.0

[mender-test-bot]

This PR contains the following updates:

Package	Update	Change
mendersoftware/mender-artifact	major	3.11.2 → 4.4.0
mendersoftware/mender-artifact	minor	4.1.0 → 4.4.0

---

Release Notes

mendersoftware/mender-artifact (mendersoftware/mender-artifact)

v4.4.0

Compare Source

Bug fixes

• List compatible-types as a required argument
  (MEN-9376) (daca4c3) by @​danielskinstad

• Populate type in type-info for rootfs-image
  (7598da8)

  Fix regression which caused the "write rootfs-image"
  command to produce an Artifact with empty "type" in type-info and
  thus not adhering to the format specification. The same versions
  that write such an Artifact will also accept it, but both issues
  have been fixed: A corrupt Artifact is not written anymore, nor
  will corrupt Artifacts be accepted. If you have produced an
  Artifact using a version of mender-artifact prior to 4.3.1, you
  may have to recreate it.

Features

• Add 'tmp' directory cli option
  (MEN-8479) (e6d7ff1) by @​rewanrashid-boop

  Change mender-artifact 'install', 'write rootfs-image', 'modify' to
  allow for custom 'tmp' directory

v4.3.0

Compare Source

Bug fixes

• Improve header path validation parsing artifact header
  (171d940) by @​alfrunes

  Currently, the artifact format allows path traversal patterns in the
  header.tar entry as only the prefix and basename of the path is
  validated. Although the mender artifact library or CLI never extracts
  the artifact header to the file system, the validation should validate
  the paths against the specification.
  This commit makes the installer parse the entire path pattern.

• Compatibility with Windows for tar paths
  (743ec49) by @​alfrunes

  Replaced path expansion library from OS dependent path/filepath to path which uses tar-compatible / separator for path segments when evaluating tar paths.

Features

• Add --compatible-types (-c) as alias for --device-type
  (MEN-9010) (1adacac) by @​vpodzime

  Add a new CLI option --compatible-types with short option -c that
  works the same way as --device-type but is mutually exclusive
  with it. This provides an alternative name for specifying
  compatible types when creating artifacts.

  The new flag is available on all write subcommands: rootfs-image,
  module-image, and bootstrap-artifact.

  The old CLI option --device-type is now marked as deprecated and
  its use produces a warning.

  Also, "Compatible devices" is now replaced by "Compatible types" in read
  command output.

v4.2.0

Compare Source

Features

• Optionally warn or fail on large Artifact sizes
  (MEN-8567) (5f23818) by @​lluiscampos

  The write commands can now warn or fail when creating Artifacts bigger
  than a certain size. This feature is meant to be used with upcoming
  Mender Tier plans, which may set up limits on the Artifact size.

  The behaviour can be controlled with the flags:

  • --warn-artifact-size to soft warn on Artifacts larger than the limit
  • --max-artifact-size to hard fail on Artifacts larger than the limit

  Note that the limits are not enforced when streaming to stdout output,
  nor on other commands that may increase the Artifact size like modify,
  cp or install.

Build

• Fix make test target
  (41c96f0) by @​lluiscampos

  The well-intended commit ba669f0 broke make test when improving
  the make coverage target :)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[mender-test-bot]

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

• mentioning me and start integration 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 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

[vpodzime]

@mender-test-bot start integration pipeline

[mender-test-bot]

Hello 😺 I created a pipeline for you here: Pipeline-2423325531

Build Configuration Matrix

Key	Value
INTEGRATION_REV	pull/2875/head
RUN_TESTS_FULL_INTEGRATION	true

[vpodzime]

@mender-test-bot start integration pipeline

[mender-test-bot]

Hello 😺 I created a pipeline for you here: Pipeline-2423393896

Build Configuration Matrix

Key	Value
INTEGRATION_REV	pull/2875/head
RUN_TESTS_FULL_INTEGRATION	true