chore: bump pkg version to v8.2.1

[antongolub]

closes #938

[jlbribeiro]

Hey @antongolub thank you for addressing this so quickly! I thought of doing this PR, but (possibly a noob question, as I've never done release management on GitHub): isn't the release associated to a Git tag? Meaning: installs of the 8.2.1 tag/release will still have the incorrect 8.2.0 package.json, correct? (which means the CLI will still report 8.2.0 if not installed from the main branch)

[antongolub]

We use a pair of triggers to publish npm pkg: release tag and manual dispatch

name: Publish

on:
  workflow_dispatch:
  release:
    types: [created]

So, as soon as this PR is merged, the npm pkg will be published by click

[jlbribeiro]

@antongolub Thank you for your reply; if that means the Git tag (and GitHub release) will be overwritten to point to the new commit, then that's fixed. (but I was under the impression Git tags don't get overwritten, hence the original question). Apologies for the noise. If this doesn't address my concerns, I'll have to pin by commit instead, which is ok.

(full context of the original (#938) issue)

The nixpkgs package is built from source, based on the git tag; it's the mismatch between the Git tag and the package.json version that ends up being the problem in my particular case; I was under the impression that overwriting Git tags was not "common". Thank you!

[antongolub]

We can just move the release tag to the next commit as an option too.

[antongolub]

@jlbribeiro

fyi, 8.2.2 is definitely in sync.

[jlbribeiro]

@antongolub Thank you for the ping (and apologies for the spam above!).