Skip to content
This repository has been archived by the owner on Nov 4, 2024. It is now read-only.

Allow publishing of pre-release version #430

Open
envil opened this issue Feb 19, 2024 · 0 comments
Open

Allow publishing of pre-release version #430

envil opened this issue Feb 19, 2024 · 0 comments

Comments

@envil
Copy link

envil commented Feb 19, 2024

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant