Release 4.2.0 #136
Merged
Release 4.2.0 #136
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
|
Oops, I forgot to put the new version in |
|
Let's remove the Regarding the required steps:
|
|
To avoid the unessercy version bump you can also do a force push with the fixed version this time. |
josephfrazier
added a commit
to josephfrazier/browser-extension
that referenced
this pull request
Jul 30, 2016
`npm version` is an easy way to commit a new version, but it only updates `package.json`. This script ensures that the version in `assets/manifest.json` is kept in sync, to avoid a reoccurrence of OctoLinker#136 (comment) See here for details about `npm version` and its associated package.json scripts: https://docs.npmjs.com/cli/version
josephfrazier
added a commit
to josephfrazier/browser-extension
that referenced
this pull request
Jul 30, 2016
`npm version` is an easy way to commit a new version, but it only updates `package.json`. This script ensures that the version in `assets/manifest.json` is kept in sync, to avoid a reoccurrence of OctoLinker#136 (comment) See here for details about `npm version` and its associated package.json scripts: https://docs.npmjs.com/cli/version
|
I disabled the branch protection and remove the release from GH. |
stefanbuck
pushed a commit
that referenced
this pull request
Jul 30, 2016
`npm version` is an easy way to commit a new version, but it only updates `package.json`. This script ensures that the version in `assets/manifest.json` is kept in sync, to avoid a reoccurrence of #136 (comment) See here for details about `npm version` and its associated package.json scripts: https://docs.npmjs.com/cli/version
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
`npm version` is an easy way to commit a new version, but it only updates `package.json`. This script ensures that the version in `assets/manifest.json` is kept in sync, to avoid a reoccurrence of OctoLinker/OctoLinker#136 (comment) See here for details about `npm version` and its associated package.json scripts: https://docs.npmjs.com/cli/version
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.
See #135
@stefanbuck, as we've discussed privately, I'll take a shot at doing the releases for this one. Just to confirm, here are the steps that are needed (as far as I know):
v4.2.0and push the tag into this reponpm run package-allout/firefox-octolinker-4.2.0.zipto https://addons.mozilla.org/en-US/developers/addon/octolinker/versions#version-uploadout/opera-octolinker-4.2.0.zipto https://addons.opera.com/developer/package/226344/?tab=versions