You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We create a web-ext-artifacts/LOWERCASE_PACKAGE-VERSION.zip
What is the expected or desired behavior?
We are allowed to specify a name, e.g. with --output <filename>. This doesn't have to be the default behavior, but it avoids having to wrap the web-ext build with another command that renames it.
We're automating how we sign and ship XPIs. Having a deterministic name, without having to download n package.json files to determine what the version is, allows us to simplify our automation. Currently we have a hardcoded version here that we have to bump every time the version bumps in package.json.
The text was updated successfully, but these errors were encountered:
Feature request: deterministic filenames
What is the current behavior?
We create a
web-ext-artifacts/LOWERCASE_PACKAGE-VERSION.zipWhat is the expected or desired behavior?
We are allowed to specify a name, e.g. with
--output <filename>. This doesn't have to be the default behavior, but it avoids having to wrap the web-ext build with another command that renames it.We're automating how we sign and ship XPIs. Having a deterministic name, without having to download
npackage.json files to determine what the version is, allows us to simplify our automation. Currently we have a hardcoded version here that we have to bump every time the version bumps in package.json.The text was updated successfully, but these errors were encountered: