Marc Durdin 34ece2182d fix(common): update sentry release identifiers to support semver ... Fixes #7895. This should mean that Sentry reports start to track semantic versions. I have reviewed each project and I _think_ I've captured all the locations where we need to construct release identifiers. Note that one of them was fixed from a plain version number. Docs on release format: https://docs.sentry.io/platforms/node/guides/serverless-cloud/configuration/releases/#bind-the-version		2023-01-17 17:04:24 +07:00
..
.gitignore	chore(web): move version from package.json to keyman-version package	2022-04-17 06:47:39 +10:00
.npmignore	fix(developer): publish @keymanapp/keyman-version to npm	2022-11-02 13:33:24 +11:00
build.sh	fix(common): update sentry release identifiers to support semver	2023-01-17 17:04:24 +07:00
index.ts	chore(web): declaration alias for module export use	2022-05-23 13:44:55 +07:00
package.json	chore(web): adapts keyman-version bundling in Developer products	2022-05-28 10:57:24 +10:00
tsconfig.json	chore(web): make build paths consistent	2022-05-04 10:13:44 +10:00