From caf989f77c53470cc471a33f6b963fc51fd2c599 Mon Sep 17 00:00:00 2001
From: dannyrb <danny.ri.brown@gmail.com>
Date: Tue, 21 May 2019 14:01:14 -0400
Subject: [PATCH] fix: Make sure we persist our npm_publish changes so
 docker_publish can access new version number

---
 .circleci/config.yml | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/.circleci/config.yml b/.circleci/config.yml
index 46d05f977..5c3156106 100644
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@ -35,7 +35,6 @@ jobs:
           paths:
             - ~/.cache/yarn
           key: yarn-packages-v1-{{ .Branch }}-{{ checksum "yarn.lock" }}
-
       # Build & Test
       - run: yarn build:package:ci
       # https://www.viget.com/articles/using-junit-on-circleci-2-0-with-jest-and-eslint/
@@ -44,13 +43,11 @@ jobs:
           command: yarn test:ci
           environment:
             JEST_JUNIT_OUTPUT: 'reports/junit/js-test-results.xml'
-
       # Store result
       - store_test_results:
           path: reports/junit
       - store_artifacts:
           path: reports/junit
-
       # Persist :+1:
       - persist_to_workspace:
           root: ~/repo
@@ -71,6 +68,10 @@ jobs:
       - run:
           name: Publish using Semantic Release
           command: npx semantic-release --debug
+      # Persist :+1:
+      - persist_to_workspace:
+          root: ~/repo
+          paths: .
 
   docs_publish:
     <<: *defaults