Vector 0.43.1 release

[pront]

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>
• 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
• Run cargo vdev build release-cue to generate a new cue file for the release
  • Add description key to the generated cue file with a description of the release (see
    previous releases for examples).
• Update version number in distribution/install.sh
• Add new version to website/cue/reference/versions.cue
• Create new release md file by copying an existing one in ./website/content/en/releases/ and
  updating version number
• Run cargo check to regenerate Cargo.lock file
• Commit these changes
• Open PR against the release branch (v0.<new version number>) for review
• PR approval

On the day of release:

• Ensure release date in cue matches current date.
• Rebase the release preparation branch on the release branch
  • Squash the release preparation commits (but not the cherry-picked commits!) to a single
    commit. This makes it easier to cherry-pick to master after the release.
  • git checkout prepare-v0.<new version number> && git rebase -i v0.<current minor version>
• Merge release preparation branch into the release branch
  • git co v0.<current minor version> && git merge --ff-only prepare-v0.<current minor version>.<patch>
• Tag new release
  • git tag v0.<minor>.<patch> -a -m v0.<minor>.<patch>
  • git push origin v0.<minor>.<patch>
• Wait for release workflow to complete
  • Discoverable via https://github.com/timberio/vector/actions/workflows/release.yml
• Release Linux packages. See vector-release usage.
  • Manually trigger the trigger-package-release-pipeline-prod-stable job.
• Push the release branch to update the remote (This should close the preparation branch PR).
  • git checkout v0.<current minor version> && git push
• Release updated Helm chart. See releasing Helm chart.
• Once Helm chart is released, updated Vector manifests
  • Run cargo vdev build manifests and open a PR with changes
• Add docker images to https://github.com/DataDog/images to have them available internally.
  • Follow the instructions at the top of the mirror.yaml file.
• Cherry-pick any release commits from the release branch that are not on master, to master
• Reset the website branch to the HEAD of the release branch to update https://vector.dev
  • git checkout website && git reset --hard origin/v0.<current minor version>.<patch> && git push
• Kick-off post-mortems for any regressions resolved by the release

[pront]

Note:

For https://github.com/vectordotdev/vector/commits/v0.43.1

There are two preparation commits:

• 455fae3
• e30bf1f

Two cherry-picked commits:

• ca3abef
• 43b8916