Skip to content

Commit cb4fd40

Browse files
authored
Only run changeset/actions once. (#88)
## Summary The `changeset/action` automatically versions, so running it twice in the same workflow causes the second instance to actually publish what should instead just be added to a PR. ## How did you test this change? <!-- Frontend - Leave a screencast or a screenshot to visually describe the changes. --> ## Are there any deployment considerations? <!-- Backend - Do we need to consider migrations or backfilling data? --> ## Does this work require review from our design team? <!-- Request review from julian-highlight / our design team -->
1 parent bcc1324 commit cb4fd40

File tree

1 file changed

+1
-8
lines changed

1 file changed

+1
-8
lines changed

.github/workflows/turbo.yml

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -60,14 +60,7 @@ jobs:
6060

6161
- name: Publish highlight npm packages
6262
if: github.ref == 'refs/heads/main'
63-
id: changesets-publish
64-
uses: changesets/action@v1
65-
with:
66-
publish: yarn publish:highlight
67-
env:
68-
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
69-
NPM_TOKEN: ${{ secrets.NPM_TOKEN_HIGHLIGHT_RUN }}
70-
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN_HIGHLIGHT_RUN }}
63+
run: yarn publish:highlight
7164

7265
- uses: launchdarkly/gh-actions/actions/[email protected]
7366
if: github.ref == 'refs/heads/main'

0 commit comments

Comments
 (0)