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

(chore) Fix incorrect release command in GitHub action #181

Closed
wants to merge 2 commits into from

Conversation

jayasanka-sack
Copy link
Member

@jayasanka-sack jayasanka-sack commented Feb 9, 2024

Requirements

Summary

Previously, the release commands in the workflow were incorrect, resulting in the failure to publish the package to the registry. This PR fixes the issue by updating the release commands.

"ci:publish": "yarn workspaces foreach --all --topological --exclude @openmrs/esm-home npm publish --access public --tag latest",
"ci:prepublish": "yarn workspaces foreach --all --topological --exclude @openmrs/esm-home npm publish --access public --tag next",
"ci:release": "yarn workspaces foreach --all --topological version",
"ci:publish": "yarn npm publish --access public",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we exclude @openmrs/esm-home (monorepo)?
We just want to publish @openmrs/esm-home-app (app)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops! my bad. Didn't realise that home-app is under the packages directory

"ci:prepublish": "yarn workspaces foreach --all --topological --exclude @openmrs/esm-home npm publish --access public --tag next",
"ci:release": "yarn workspaces foreach --all --topological version",
"ci:publish": "yarn npm publish --access public",
"ci:prepublish": "yarn npm publish --access public --tag next",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

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

Successfully merging this pull request may close these issues.

2 participants