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

fix: issue with prepack command that blocks release #252

Merged
merged 3 commits into from
Mar 10, 2022

Conversation

Souvikns
Copy link
Member

@Souvikns Souvikns commented Mar 9, 2022

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

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",
Copy link
Member

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?

Copy link
Member Author

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

"version": "oclif readme && git add README.md",

also I think this is why the TOC is not working

Copy link
Member

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, same prepack. Same with readme script I guess
  • oclif readme should be added to generate:assets. Although I do not really know what oclif readme is actually doing 😆 But if it is doing some important update to readme, it should be in generate:assets script. This workflow will make sure readme is updated in GH repo. We can also run generate:assets in prepublishOnly script if we need also some magic updates in readme to show up in NPM package readme view

makes sense?

Copy link
Member Author

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

@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 9, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@Souvikns Souvikns requested a review from derberg March 10, 2022 05:02
@derberg derberg changed the title fix: issue with prepack command in gh action fix: issue with prepack command that blocks release Mar 10, 2022
@Souvikns
Copy link
Member Author

I have deleted the 0.16.0 tag and will merge this PR now, hope this fixes the issue 🤞🏻

@Souvikns
Copy link
Member Author

/rtm

@asyncapi-bot asyncapi-bot merged commit e73d979 into asyncapi:master Mar 10, 2022
@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 0.16.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants