Sentry CLI: Unable to determine version
See original GitHub issueHello, I am deploying a Nuxt.js / Vue app on Zeit Now/Vercel and have setup my webpack config as follows:
...
const release = process.env.COMMIT_SHA || process.env.NOW_BITBUCKET_COMMIT_SHA || process.env.BUILD_STAGE;
// eslint-disable-next-line no-console
console.log('🚀 releasing', release);
if (process.env.SENTRY_PUBLISH_SOURCEMAPS === 'true') {
config.build.plugins.push(new SentryWebpackPlugin({
debug: true,
release,
include: '.',
ignoreFile: '.sentrycliignore',
ignore: [
'node_modules',
'node_modules_dev',
'node_modules_prod',
'tests',
'*.config.js',
'.eslintrc.js',
],
}));
}
I have confirmed via the console.log command that “release” is being set to a valid commit sha, however in the build I still see this error.
ERROR in Sentry CLI Plugin: Unable to determine version. Make sure to include release
option or use the environment that supports auto-detection https://docs.sentry.io/cli/releases/#creating-releases
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Release Management - Sentry Documentation
Releases are created with the sentry-cli releases new command. It takes at the very least a version identifier that uniquely identifies the releases....
Read more >Sentry with @sentry/webpack-plugin and heroku
You can fix this by manually specifying the release name in the plugin config: const version = require('../VERSION').version ...
Read more >@sentry/cli - npm
A command line utility to work with Sentry. https://docs.sentry.io/hosted/learn/cli/. Latest version: 2.11.0, last published: 9 days ago.
Read more >sentry-cli-binary - npm Package Health Analysis - Snyk
Learn more about sentry-cli-binary: package health score, popularity, security, maintenance, versions and more.
Read more >@sentry/cli | Yarn - Package Manager
Important: This documentation covers modern versions of Yarn. For 1.x docs, see classic.yarnpkg.com. Yarn.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m using Next.js and was running into this issue when following the
with-sentry-simple
example. Addingrelease: options.buildId
to theSentryWebpackPlugin
options like @vitalbone has in his code snippet fixed this issue for me.had the same issue, used options.buildId for the release version. next.js config file: