-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
fix: issue with prepack command that blocks release #252
Conversation
package.json
Outdated
@@ -131,7 +131,7 @@ | |||
"lint": "eslint --max-warnings 0 --config .eslintrc .", | |||
"lint:fix": "eslint --max-warnings 5 --config .eslintrc . --fix", | |||
"postpack": "rimraf oclif.manifest.json", | |||
"prepack": "rimraf lib && tsc -b && oclif manifest && oclif readme", | |||
"prepack": "npm run build && oclif manifest && oclif readme", | |||
"prepublishOnly": "npm run build", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need this if we build it in prepack
stage?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah since we are building in prepublish
stage which is run before prepack we don't need this. Though we are also running oclif readme
in version
so we might now need that too
Line 140 in 9fecc14
"version": "oclif readme && git add README.md", |
also I think this is why the TOC is not working
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
imho:
- we should only have
prepublishOnly
that runs:npm run build && oclif manifest
version
script is not needed, can be removed, sameprepack
. Same withreadme
script I guessoclif readme
should be added togenerate:assets
. Although I do not really know whatoclif readme
is actually doing 😆 But if it is doing some important update to readme, it should be ingenerate:assets
script. This workflow will make sure readme is updated in GH repo. We can also rungenerate:assets
inprepublishOnly
script if we need also some magic updates in readme to show up in NPM package readme view
makes sense?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have removed oclif readme
. It creates documentation which is handled here #123
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
I have deleted the |
/rtm |
🎉 This PR is included in version 0.16.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Trying to fix the issue with
npm prepack
command holding of the gh action and not able to publish.Still now clear what is causing the issue, since not much log is present, as of now two action run has failed for this
I tried running the command separately on my fork and it ran not sure why it is having issues here - https://github.com/Souvikns/cli/runs/5469720664?check_suite_focus=true