chore(releasing): cherry picking 0.44.0 commits (#22207)

* chore(releasing): Prepare v0.44.0 (#22192)

* chore(releasing): Prepare v0.44.0

* Bump Alpine Linux base image to 3.21

* cargo update -p vrl

* cargo vdev build release-cue

* upgrade guide

* commit website/cue/reference/releases/0.44.0.cue

* bump versions

* spelling fixes

* update changelog

* enforce changelog rendering order

* tweak upgrade guide

* add website prefix to the preparation branch so that we can get previews

* address Jesse's review points

* improve changelog change header and content alignment

chore(releasing): docs feedback on v0.44.0 (#22193)

chore(releasing): docs feedback

* reset VRL to track main

* bump vector version

Author: pront

.github/ISSUE_TEMPLATE/minor-release.md

@@ -13,7 +13,7 @@ The week before the release:
 - [ ] Create a new release branch from master to freeze commits
   - `git fetch && git checkout origin/master && git checkout -b v0.<new version number> && git push -u`
 - [ ] Create a new release preparation branch from `master`
-  - `git checkout -b prepare-v0.<new version number> && git push -u`
+  - `git checkout -b website-prepare-v0.<new version number> && git push -u`
 - [ ] Pin VRL to latest released version rather than `main`
 - [ ] Check if there is a newer version of [Alpine](https://alpinelinux.org/releases/) or
       [Debian](https://www.debian.org/releases/) available to update the release images in

.github/ISSUE_TEMPLATE/patch-release.md

@@ -8,7 +8,7 @@ labels: "domain: releasing"
 Before the release:
 
 - [ ] Create a new release preparation branch from the current release branch
-  - `git fetch && git checkout v0.<current minor version> && git checkout -b prepare-v0.<new version number>`
+  - `git fetch && git checkout v0.<current minor version> && git checkout -b website-prepare-v0.<new version number>`
 - [ ] Cherry-pick in all commits to be released from the associated release milestone
   - If any merge conflicts occur, attempt to solve them and if needed enlist the aid of those familiar with the conflicting commits.
 - [ ] Bump the release number in the `Cargo.toml` to the current version number

.github/actions/spelling/allow.txt

@@ -509,3 +509,4 @@ teledisk
 UMTS
 WCDMA
 XMODEM
+cbor

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "vector"
-version = "0.44.0"
+version = "0.45.0"
 authors = ["Vector Contributors <[email protected]>"]
 edition = "2021"
 description = "A lightweight and ultra-fast tool for building observability pipelines"

Cargo.toml

@@ -1,4 +1,4 @@
-FROM docker.io/alpine:3.20 AS builder
+FROM docker.io/alpine:3.21 AS builder
 
 WORKDIR /vector
 
@@ -12,7 +12,7 @@ RUN ARCH=$(if [ "$TARGETPLATFORM" = "linux/arm/v6" ]; then echo "arm"; else cat
 
 RUN mkdir -p /var/lib/vector
 
-FROM docker.io/alpine:3.20
+FROM docker.io/alpine:3.21
 # we want the latest versions of these
 # hadolint ignore=DL3018
 RUN apk --no-cache add ca-certificates tzdata

changelog.d/21128_log_aws_s3_objects_consumed.enhancement.md

@@ -1,4 +1,4 @@
-FROM docker.io/alpine:3.20 AS builder
+FROM docker.io/alpine:3.21 AS builder
 
 WORKDIR /vector
 

changelog.d/21704_file_sink_supports_encoding_input.feature.md

@@ -13,7 +13,7 @@ set -u
 # If PACKAGE_ROOT is unset or empty, default it.
 PACKAGE_ROOT="${PACKAGE_ROOT:-"https://packages.timber.io/vector"}"
 # If VECTOR_VERSION is unset or empty, default it.
-VECTOR_VERSION="${VECTOR_VERSION:-"0.43.1"}"
+VECTOR_VERSION="${VECTOR_VERSION:-"0.44.0"}"
 _divider="--------------------------------------------------------------------------------"
 _prompt=">>>"
 _indent="   "

changelog.d/21822-nats-sink-multiple-urls.enhancement.md

@@ -0,0 +1,42 @@
+---
+date: "2025-01-13"
+title: "0.44 Upgrade Guide"
+description: "An upgrade guide that addresses breaking changes in 0.40.0"
+authors: [ "pront" ]
+release: "0.44.0"
+hide_on_release_notes: false
+badges:
+  type: breaking change
+---
+
+## Table of Contents
+
+Breaking Changes:
+
+1. [Clickhouse Sink `skip_unknown_fields` changes](#clickhouse-sink)
+2. [File source `ignored_header_bytes` and `lines` fix](#file-source)
+3. [Some VRL functions are now fallible](#vrl-breaking-changes)
+
+## Clickhouse Sink `skip_unknown_fields` changes {#clickhouse-sink}
+
+The [skip_unknown_fields](https://vector.dev/docs/reference/configuration/sinks/clickhouse/#skip_unknown_fields) behavior was changed:
+
+- `skip_unknown_fields` is `true`: enables skipping unknown fields (overrides the server's default)
+- `skip_unknown_fields` is `false`: enables "strict" mode and does not allow skipping unknown fields for the request, (overrides the
+   server's
+   default)
+- `skip_unknown_fields` is not set: follows the server's default
+
+Double-check your configuration and update the setting per above.
+
+## File source `ignored_header_bytes` and `lines` fix {##file-source}
+
+When sourcing from compressed files, `ignored_header_bytes` no longer looks at the compressed file's bytes (which would include the
+magic bytes for the compression header). Instead, it ignores the bytes from the uncompressed content. Similarly, `lines` no longer
+looks for new line delimiters in the compressed content, but the uncompressed content.
+
+## Some VRL functions are now fallible {#vrl-breaking-changes}
+
+`to_unix_timestamp`, `to_float`, and `uuid_v7` can now return an error if the supplied timestamp is unrepresentable as a nanosecond
+timestamp. Previously the function calls would panic. VRL scripts using the above functions need to be updated to handle potential
+errors.

changelog.d/21864_kubernetes_logs_user_agent.fix.md

@@ -0,0 +1,4 @@
+---
+title: Vector v0.44.0 release notes
+weight: 21
+---

changelog.d/21873-correctly-propagate-http-config-provider.fix.md

@@ -19,7 +19,7 @@ administration: interfaces: kubectl: {
 	role_implementations: [Name=string]: {
 		commands: {
 			_deployment_variant:       string
-			_vector_version:           "0.43"
+			_vector_version:           "0.44"
 			_namespace:                string | *"vector"
 			_controller_resource_type: string
 			_controller_resource_name: string | *_deployment_variant