I discovered that we can use `npm version` to update the version number in package.json. Additionally, it can also run pre, during & post scripts to do additional tasks. Hence, to begin with I want to: - Pre-version bump: run tests (sanity check) - During version bump: change the version in install.rdf.in. - Hook up enough to bump the add-on version on for master. - Start adding some release documentation
Comment on attachment 8710704 [details] [review] [loop] Standard8:bug-1241649-ver > mozilla:master Fairly small PR to make it easy for us to bump version numbers. Includes the start of release documentation. I've also included an example commit of bumping the version numbers that I want to push anyway, as that will match the developer version of the add-on that I've just put on AMO.
Comment on attachment 8710704 [details] [review] [loop] Standard8:bug-1241649-ver > mozilla:master r=Mardak with some small script suggestions
Status: NEW → RESOLVED
Iteration: --- → 46.3 - Jan 25
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.