No Git tag associated with released versions

[amarshall]

Hi, this repo has associated versions in the NPM registry, but none here (and the package.json file has 0.0.0). This makes determining the source code associated with a registry release more difficult than it perhaps should be (though it can potentially be gleaned from the release workflow, this is not as trivial as just referencing a Git tag.

[Hinton]

Hi @amarshall,

We partially solved this with #17 which includes the build id in the version number. This should allow easy mapping by getting the appropriate run in https://github.com/bitwarden/sdk-internal/actions/workflows/publish-wasm-internal.yml and checking the git hash. Is this satisfactory?

[amarshall]

GitHub Actions logs are only retained for up to 90 days (see docs), so it only works for a limited period of time.

[brjsp]

@amarshall Thanks for alerting me to this. I've manually archived the existing versions at https://github.com/brjsp/sdk-internal/tags

(I'm not affiliated with Bitwarden but i maintain the package in openSUSE.)

[Hinton]

Hmm, would including a VERSION file on npm, containing the git hash work?