Skip to content

ci: update GH Action & Cypress dependencies for a successful build.#117

Merged
cball merged 3 commits intocanaryfrom
116-gh-actions-update
Dec 16, 2020
Merged

ci: update GH Action & Cypress dependencies for a successful build.#117
cball merged 3 commits intocanaryfrom
116-gh-actions-update

Conversation

@cball
Copy link
Copy Markdown
Member

@cball cball commented Dec 13, 2020

There were three major changes required here. The setup-node step was done by @cmejet in #112. I split it out to a separate PR so that we can keep the Chakra UI upgrade isolated.

This PR also replaces the forked version of vercel-action that we were using previously(https://github.com/ngduc/vercel-deploy-action) with the original one (https://github.com/amondnet/vercel-action). It has the required updates for the recent set-env deprecation from GitHub (https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).

Finally, @testing-library/cypress combined with our main Cypress version was causing us to download it twice, then fail the build on a checksum error. For more background, see: cypress-io/cypress#4595

Changes

  • update setup-node to v2.1.2
  • update vercel-action to v20
  • update @testing-library/cypress to ^7.0.2
  • update cypress to ^6.1.0

Screenshots

CleanShot 2020-12-13 at 11 45 42

Checklist

  • Requires dependency update?
  • Generating a new app works
  • Tests in the generated app work

Fixes #116

This also sets the default vercel scope to secrets.VERCEL_ORG_ID
Previously, we were accidently installing 2 versions of Cypress.

See: cypress-io/cypress#4595
@cball cball requested a review from a team December 13, 2020 16:50
- uses: actions/checkout@v2
<% if (host.name === 'vercel') { -%>
- uses: ngduc/vercel-deploy-action@master
- uses: amondnet/vercel-action@v20
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💯

vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID}}
# SET THIS OR YOU WILL DEPLOY TO YOUR PERSONAL VERCEL NAMESPACE
# scope: ${{ secrets.VERCEL_TEAM_ID }}
# scope: ${{ secrets.VERCEL_ORG_ID }}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just for background, how will users know to uncomment this? Is it in the tutorial?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It could definitely use some more documentation. I think the correct answer here is to prompt for this value when creating the project. I'll add a followup issue for that.

Copy link
Copy Markdown

@mcavaliere mcavaliere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, FWIW.

@cball cball mentioned this pull request Dec 16, 2020
@cball cball merged commit dd0da09 into canary Dec 16, 2020
@cball cball deleted the 116-gh-actions-update branch December 16, 2020 15:11
code-jenn-or pushed a commit that referenced this pull request Mar 24, 2021
…117)

* update actions/setup-node to 2.1.2

* update vercel-action to amondnet/vercel-action@v20.

This also sets the default vercel scope to secrets.VERCEL_ORG_ID

* fixes Cypress issues

Previously, we were accidently installing 2 versions of Cypress.

See: cypress-io/cypress#4595
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.

GitHub Actions need to be updated (likely in template repo as well)

2 participants