Skip to content

Commit

Permalink
fix: try to store npm tarball in /tmp dir named with git hash
Browse files Browse the repository at this point in the history
  • Loading branch information
cwillisf committed Sep 11, 2024
1 parent 64df495 commit b95b3c4
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions release.config.js
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,10 @@ module.exports = {
[
'@semantic-release/npm',
{
// Do not set 'tarballDir' without considering this issue: https://github.com/semantic-release/npm/issues/535
// Do not set 'tarballDir' to a relative path without considering this issue:
// https://github.com/semantic-release/npm/issues/535
// If the tarball is within the package directory, it will be included in the second 'prepack' run.
tarballDir: '/tmp/semantic-release-${nextRelease.gitHead}/'

Check failure on line 21 in release.config.js

View workflow job for this annotation

GitHub Actions / ci-cd

Unexpected template string expression

Check failure on line 21 in release.config.js

View workflow job for this annotation

GitHub Actions / ci-cd

Unexpected template string expression
}
],
[
Expand All @@ -30,7 +33,7 @@ module.exports = {
[
'@semantic-release/github',
{
assets: 'pack/*.tgz'
assets: '/tmp/semantic-release-${nextRelease.gitHead}/*.tgz'

Check failure on line 36 in release.config.js

View workflow job for this annotation

GitHub Actions / ci-cd

Unexpected template string expression

Check failure on line 36 in release.config.js

View workflow job for this annotation

GitHub Actions / ci-cd

Unexpected template string expression
}
]
]
Expand Down

0 comments on commit b95b3c4

Please sign in to comment.