semantic-release-firefox-add-on
semantic-release-firefox-add-on copied to clipboard
Allow publishing of pre-release version
Is your feature request related to a problem? Please describe. Inspired by this issue
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 preventing me from publishing a new version of my chrome extension to a staging extension while maintaining the pre-release functionality on my develop branch.
Describe the solution you'd like
Add an optional boolean allowPrerelease
field to the PluginConfig interface. When allowPrerelease
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, if 1.0.0-develop.1
is the given pre-release version, then 1.0.0
will be parsed and used for the version.
Additionally, we can set the original release version (1.0.0-develop.1
) to the version_name field for displaying purpose.