Publish pre-release(beta) build automatically #38
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.
This pull request introduces new workflows and enhancements to the CI/CD pipeline for managing pre-releases and releases. The most notable changes include adding a new workflow for automating pre-releases to NPM from the
developbranch, and improving the existingpublishworkflow by extracting the version from tags and creating draft releases on GitHub.New Workflow for Pre-Releases:
.github/workflows/pre-release.yml: Added a new workflow to automate pre-releases to NPM. It generates a pre-release version from thedevelopbranch, updatespackage.json, builds the project, publishes the pre-release to NPM with abetatag, and creates a corresponding GitHub pre-release.Enhancements to the Publish Workflow:
.github/workflows/publish.yml:fetch-depth: 0to theactions/checkout@v4step to ensure full Git history is available.