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
#111 - Allow publishing of pre-release version
Description
A new feature that allows the publishing of pre-release versions is introduced in this PR.
Why
When utilizing the semantic-release package's pre-release functionality, the semantic-release-chrome's chrome web api call throws a version format error.
This is prevents the plugin from publishing a new chrome extension version to a staging extension while maintaining the pre-release functionality on my develop branch.
How
Adds an optional boolean
allowPrerelease
field to thePluginConfig
interface. WhenallowPrerelease
is specified and set to true, the semantic version number is parsed from the given version string instead of using the raw string. For example, if1.0.0-develop.1
is the given pre-release version, then1.0.0
will be parsed and used for the chrome web store publishing purposes.Screenshots
How has this been tested
Type of change
Checklist
npm run ci
to be sure).