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
Currently the manifest.json version value is being bumped according to sematic-commits. A push to beta bumps the version number to something like 1.2.0-beta.4.
Which is not allowed by web-browsers. Since the manifest version number should only be dot seperated integers between 0 and 655536. Like 1.2.0. That is the version number when released to main. Hence, the version value should only be bumped when released on the main branch.
Steps to reproduce
Build a the current version of the extension using npm build.
Try to add the extension to your brower at chrome://extensions.
Affected services
browser-extension
Platforms
No response
Browsers
Chrome, Edge
Environment
Production, Development
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
Contributing Docs
I agree to follow this project's Contribution Docs
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently the manifest.json
version
value is being bumped according to sematic-commits. A push to beta bumps the version number to something like1.2.0-beta.4
.Which is not allowed by web-browsers. Since the manifest version number should only be dot seperated integers between 0 and 655536. Like
1.2.0
. That is the version number when released tomain
. Hence, the version value should only be bumped when released on the main branch.Steps to reproduce
npm build
.chrome://extensions
.Affected services
browser-extension
Platforms
No response
Browsers
Chrome, Edge
Environment
Production, Development
Additional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: