@@ -40,7 +40,7 @@ You can create a new Sentry release by setting the `version` option. By default,
40
40
fetch-depth : 0
41
41
42
42
- name : Create Sentry release
43
- uses : getsentry/action-release@v1
43
+ uses : getsentry/action-release@v3
44
44
env :
45
45
SENTRY_AUTH_TOKEN : ${{ secrets.SENTRY_AUTH_TOKEN }}
46
46
SENTRY_ORG : ${{ secrets.SENTRY_ORG }}
@@ -55,8 +55,7 @@ You can create a new Sentry release by setting the `version` option. By default,
55
55
If your application is written in JavaScript you probably deploy minified application code. To enable readable
56
56
stack traces in your Sentry errors, you need to upload source maps to Sentry.
57
57
58
- Provide the path(s) to your source maps via the ` sourcemaps` option and set the `inject` flag to allow the GitHub
59
- action to inject information into your source files and source maps to ensure proper un-minification of your stack traces.
58
+ Provide the path(s) to your source maps via the ` sourcemaps` option to ensure proper un-minification of your stack traces.
60
59
Visit [What are Artifact Bundles](/platforms/javascript/sourcemaps/troubleshooting_js/artifact-bundles/) if you want to learn more.
61
60
62
61
` ` ` yml
@@ -65,14 +64,13 @@ Visit [What are Artifact Bundles](/platforms/javascript/sourcemaps/troubleshooti
65
64
fetch-depth: 0
66
65
67
66
- name: Create Sentry release
68
- uses: getsentry/action-release@v1
67
+ uses: getsentry/action-release@v3
69
68
env:
70
69
SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
71
70
SENTRY_ORG: ${{ secrets.SENTRY_ORG }}
72
71
SENTRY_PROJECT: ${{ secrets.SENTRY_PROJECT }}
73
72
with:
74
73
environment: production
75
- inject: true
76
74
sourcemaps: './dist'
77
75
` ` `
78
76
0 commit comments