Getting a lot of these. At first I thought it was because I tried deploying branches with the same commit state more than once, yet it now also happens for fresh deploys. Any idea maybe what the issue might be ?
1:01:21 PM: [fatal] Nuxt build error
1:01:21 PM: ERROR in Sentry CLI Plugin: Command failed: node_modules/@sentry/cli/sentry-cli releases set-commits fce7c0ff8b1359290bb8ad4e6562dd57510b76ae --auto
1:01:21 PM: error: Could not find the SHA of the previous release in the git history. If you limit the clone depth, try to increase it. Otherwise, it means that the commit we are looking for was amended or squashed and cannot be retrieved. Use --ignore-missing flag to skip it and create a new release with the default commits count.
Config:
sentry: {
disabled: publicEnvVars.APP_CONTEXT === 'development', // will be false for tests .e.g unit, integration
dsn: 'MASKED',
// release: is automatically inferred from the local repo .package.json unless specified manually,
repo: 'MASKED',
publishRelease: true,
attachCommits: true,
sourceMapStyle: 'hidden-source-map',
// --- native sentry config Options
config: {
environment: publicEnvVars.APP_CONTEXT,
// -> NOTE: additional config in ~.sentryclirc
// as 'auth' and 'orgSlug' can't be yet set here
},
}
Getting a lot of these. At first I thought it was because I tried deploying branches with the same commit state more than once, yet it now also happens for fresh deploys. Any idea maybe what the issue might be ?
Config: