Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[doc] GH Release may produce different TGZ files than what gets published on NPM #74

Open
zFernand0 opened this issue Oct 3, 2022 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request priority-medium

Comments

@zFernand0
Copy link
Collaborator

It's possible for npm packages to have variations between npmjs.org and what may get published to GH Releases using the following code snippet

```json
{
"plugins": [
["@octorelease/npm", {
"npmPublish": false,
"tarballDir": "dist"
}],
["@octorelease/github", {
"assets": "dist/*.tgz"
}]
]
}
```

I believe a warning might be good in order to remind developers that npm lifecycle hooks may not be executed when publishing with the GH plugin 😋

@t1m0thyj t1m0thyj added documentation Improvements or additions to documentation enhancement New feature or request priority-medium labels Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request priority-medium
Projects
None yet
Development

No branches or pull requests

2 participants