Skip to content

Commit

Permalink
Bumped version to v0.7.0 (#196)
Browse files Browse the repository at this point in the history
Bumped version to v0.7.0
  • Loading branch information
ErikBjare authored Jul 3, 2019
2 parents 6e46349 + 31ad44c commit a6ecfa2
Show file tree
Hide file tree
Showing 5 changed files with 18 additions and 17 deletions.
1 change: 1 addition & 0 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,7 @@ prepublish:
make clean
-scripts/set_version.py dist/manifest.json
-scripts/set_version.py package.json
npm run precommit
make build-production
make package

Expand Down
2 changes: 1 addition & 1 deletion dist/manifest.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"manifest_version": 2,
"name": "Thankful",
"version": "0.6.9",
"version": "0.7.0",
"description": "Support free culture by automatically sending cryptocurrency to the creators of the content you love.",
"icons": {
"64": "icons/handshake.png"
Expand Down
28 changes: 14 additions & 14 deletions docs/release-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,17 +2,17 @@

How to make a release:

- Make sure tests pass.
- Create and checkout a branch for the new version.
- Run `env TRAVIS_TAG=<version> make prepublish` and make sure it succeeds.
- Commit the changed files (`package.json` and `dist/manifest.json`).
- Create a PR, merge when checks have passed.
- Check out the master branch.
- Create a release/tag on GitHub.
- Publish to Chrome webstore (not automated)
- First time only:
- Create a `.env-webstore` with your `CLIENT_ID=...` and `CLIENT_SECRET=...` on separate lines
- Run `make webstore-step1`, authenticate and put the received value as `CODE=...` in `.env-webstore`
- Run `make webstore-step2`, put value of the printed `refresh_token` key into `REFRESH_TOKEN=...`
- Run `make publish-webstore`
- Upload the source zip from the GitHub tag to Mozilla Addons.
- Make sure tests pass.
- Create and checkout a branch for the new version.
- Run `env TRAVIS_TAG=<version> make prepublish` and make sure it succeeds.
- Commit the changed files (`package.json` and `dist/manifest.json`).
- Create a PR, merge when checks have passed.
- Create a release/tag on GitHub.
- Check out the master branch.
- Publish to Chrome webstore (not automated)
- First time only:
- Create a `.env-webstore` with your `CLIENT_ID=...` and `CLIENT_SECRET=...` on separate lines
- Run `make webstore-step1`, authenticate and put the received value as `CODE=...` in `.env-webstore`
- Run `make webstore-step2`, put value of the printed `refresh_token` key into `REFRESH_TOKEN=...`
- Run `make publish-webstore`
- Upload the source zip from the GitHub tag to Mozilla Addons.
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "thankful",
"version": "0.6.9",
"version": "0.7.0",
"description": "Thankful",
"main": "index.js",
"scripts": {
Expand Down
2 changes: 1 addition & 1 deletion scripts/set_version.py
Original file line number Diff line number Diff line change
Expand Up @@ -20,4 +20,4 @@
with manifest_file.open("w") as f:
json.dump(data, f, indent=2)

print("Version v' + version + ' set successfully in: " + str(manifest_file))
print(f"Version v{version} set successfully in: {manifest_file}")

0 comments on commit a6ecfa2

Please sign in to comment.