Release checklist

Make sure tests pass.
Go to releases and edit an existing release draft, name tag, and bump version if required.
GHA will deploy packages to PyPI and binary packages to the corresponding GitHub release page automatically.
Go to iterative/dvc.org and update downloadlinks. Name your commit as download: update to 0.54.3.
Brew guys seem to now update our package automatically, but please keep an eye on it Homebrew/homebrew-core
Our bot will once a day check dvc github releases and will create a PR for chocolatey-dvc, you will only need to merge it. Please keep an eye on the package page, since their test suit is flaky.
Conda bots will automatically create a PR in dvc-feedstock when dvc is updated on pypi. Be sure to follow the instructions in the PR before merging it. For additional info see conda maintenance.
Go to iterative/lambda-latest-version, and merge automatically genenerated PR.
GHA will deploy deb/rpm to aws automatically.

Major version transitions

request a new channel version-prefix (aka track) at https://forum.snapcraft.io/t/track-request-for-dvc/17735 (e.g. v2)
- otherwise attempting to snapcraft release --channel=v2 will fail
create a new legacy-dev git branch (e.g. 1.x-dev)
(optional) give a warning message: cherry-pick dvc@6f0a05ad. Wait ~30 days before continuing to the next step
- the idea is to warn & give 2 options: opt-in now, or opt-out permanently. Both options will suppress the warning. Ignoring the warning will result in an auto-upgrade in 30 days
uncomment the echo "unset SNAP_CHANNEL" >>env.sh line in scripts/ci/before_install.sh