Allow PreRelease, and update manifest.version_name #2
Conversation
This file contains 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
|
🎉 This PR is included in version 3.3.0-prAllowPrereleaseAndVersionName.1 🎉 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
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.
Pull Request
Related issue
GabeDuarteM#111
Description
This change builds on the AllowPrerelease change requested in GabeDuarteM#111 which adapts manifest.version to the Chrome Extension version numbering scheme. This change also updates the manifest.version_name field.
Why
When building multiple successive alpha or beta prerelease versions, we want a way of knowing the build version of those releases.
How
The "standard" manifest.version_name field is updated with the original semantic-release generated version number.
How has this been tested
Type of change
Checklist
npm run cito be sure).