Feat : Add GitHub Actions workflow for automatic wrapper publishing #175
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Triggers on package.json changes in wrapper directories Includes version checking to prevent duplicate publishing Currently in test mode (npm publish commented out) Based on chargebee-js publish-new-version.yml pattern
| on: | ||
| push: | ||
| branches: | ||
| - feat/CHKOUTENGG-52904 |
Contributor
There was a problem hiding this comment.
@cb-adarshjayan @cb-ishusingh Shouldn't this be either release/x.x or based on workflow-actions run?
Contributor
Author
There was a problem hiding this comment.
We were testing with this branch name , will update it with the correct one once done testing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Triggers on package.json changes in wrapper directories (Vue, React, Angular) and automatically publishes to npm when versions are updated.
Includes version checking to prevent duplicate publishing by verifying if the version already exists in the npm registry before attempting to publish.
Currently in test mode with npm publish commands commented out, showing what would be published without actually publishing to npm.
Based on chargebee-js publish-new-version.yml pattern for consistency with existing workflows.