[CircleCI] Remove publish-stable and publish-canary steps
#2957
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
Publishing to npm is now handled by GitHub Actions. Aside from that, the Circle publishing was broken. See: https://circleci.com/gh/zeit/now/7213
AndyBitz
approved these changes
Sep 4, 2019
Codecov Report
@@ Coverage Diff @@
## canary #2957 +/- ##
==========================================
+ Coverage 11.23% 11.32% +0.08%
==========================================
Files 267 267
Lines 10069 10079 +10
Branches 1310 1303 -7
==========================================
+ Hits 1131 1141 +10
- Misses 8847 8848 +1
+ Partials 91 90 -1
Continue to review full report at Codecov.
|
styfle
pushed a commit
that referenced
this pull request
Sep 17, 2019
Publishing to npm is now handled by GitHub Actions. Aside from that, the Circle publishing was broken. See: https://circleci.com/gh/zeit/now/7213
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.
Publishing to npm is now handled by GitHub Actions.
Aside from that, the Circle publishing was broken. See: https://circleci.com/gh/zeit/now/7213