Synchronize assets/manifest.json version with package.json #138
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was done with `npm run version`, which normally happens as part of `npm version` (see OctoLinker#137) It looks like the `json` command reformatted a couple of other fields, but that should be a one-time thing, assuming we preserve the new formatting with any manual changes we make in the future. Once this is merged, we can tag it as `v4.2.0` and try the release again, as described in OctoLinker#137 (comment)
|
Go for it 😄 |
|
Awesome, thanks! I submitted the Firefox/Opera versions from the Github release .zip files, as you mentioned in #136 (comment). Here they are:
I didn't see where to submit the Opera source code, though |
|
Ahh right, there is no possibilty to upload ther source in the opera store (I should go to bed). Just post the tag zip link in the Good night and enjoy your weekend. |
|
Ohhh, I see now. I took care of it. Thanks for all the help, and enjoy your weekend too! |
josephfrazier
added a commit
to josephfrazier/browser-extension
that referenced
this pull request
Jul 31, 2016
These steps were assembled from the comments in: * OctoLinker#136 * OctoLinker#137 * OctoLinker#138
stefanbuck
pushed a commit
that referenced
this pull request
Aug 3, 2016
* Document the release process in CONTRIBUTING.md These steps were assembled from the comments in: * #136 * #137 * #138 * CONTRIBUTING.md: Add commit log link See #139 (comment)
omadoww
added a commit
to omadoww/browser-extension
that referenced
this pull request
Nov 20, 2024
* Document the release process in CONTRIBUTING.md These steps were assembled from the comments in: * OctoLinker/OctoLinker#136 * OctoLinker/OctoLinker#137 * OctoLinker/OctoLinker#138 * CONTRIBUTING.md: Add commit log link See OctoLinker/OctoLinker#139 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was done with
npm run version, which normally happens as part ofnpm version(see #137)It looks like the
jsoncommand reformatted a couple of other fields,but that should be a one-time thing, assuming we preserve the new
formatting with any manual changes we make in the future.
Once this is merged, we can tag it as
v4.2.0and try the release again,as described in #137 (comment)