The version is a claim about the artifact, and claims get stale. The check is a command that prints what the artifact actually carries, run against what you believe, which is the only way a mismatch is found before a release.
About 1 min of reading
Assert the version.
The check
Before you run it, say out loud what it will print. Then open the answer.
Read the first example one line at a time. A line that prints shows what appears on screen; the rest set things up quietly.
A single command that prints version, build hash, and dependency lock is the report a release is made against. Three separate commands is three chances to forget one.
A version check that prints a warning is a check that gets ignored. A check that exits non zero is one that a release script will not step past.
A command that reports the running version is the check that the right build is deployed. Without it, a deploy is a belief about a server you are not looking at.
The version in the build metadata and the version in the file name should be equal. A script that asserts it is what catches the mismatch that a release then ships.
Before a release, assert the tag is on the remote. A release with no reachable tag is a release that cannot be rebuilt, and the assertion is one line.
Each one is defined here on this site. Open the entry for the full definition and the other words it points at.