Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add npm publish to release steps #207

Merged
merged 1 commit into from Jun 2, 2019

Conversation

hwillson
Copy link
Member

@hwillson hwillson commented Jun 2, 2019

Whenever we publish a new version of the devtools for Chrome/FF, we need to also publish a new version to npm (so external tools integrating with devtools can get access to the latest version). We will want to automate this at some point in the future.

Whenever we publish a new version of the devtools for Chrome/FF,
we need to also publish a new version to npm (so external tools
integrating with devtools can get access to the latest version).
We will want to automate this at some point in the future.
@hwillson hwillson merged commit 6f721c1 into master Jun 2, 2019
@hwillson hwillson deleted the hwillson/npm-publish-instructions branch June 2, 2019 10:12
mjlyons pushed a commit to mjlyons/apollo-client-devtools that referenced this pull request Jun 20, 2019
Whenever we publish a new version of the devtools for Chrome/FF,
we need to also publish a new version to npm (so external tools
integrating with devtools can get access to the latest version).
We will want to automate this at some point in the future.
woahitsraj pushed a commit to woahitsraj/apollo-client-devtools that referenced this pull request Oct 15, 2019
Whenever we publish a new version of the devtools for Chrome/FF,
we need to also publish a new version to npm (so external tools
integrating with devtools can get access to the latest version).
We will want to automate this at some point in the future.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant