Use new syntax to set environment variables in CI

[acostalima]

The workflow which deploys to Vercel is currently failing:

The set-env command was deprecated a few months ago and recently disabled. This PR updates the workflow to use the new syntax.

[github-actions[bot]]

This pull-request can be previewed at https://next-with-moxy-pr-117.vercel.app. Please check the Vercel status below to see when it's ready.

[codecov[bot]]

Codecov Report

Merging #117 (17964d5) into master (7d9cfc8) will not change coverage. The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #117   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          115       115           
  Branches        11        11           
=========================================
  Hits           115       115           

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 7d9cfc8...17964d5. Read the comment docs.

[acostalima]

Now it's failing due to lack of permissions. 😕 @satazor, do you have any clue what's going on?

[satazor]

@acostalima I don't think the env variable is passing trough the vercel cli call, as the CI is failing saying we don't have access.

[acostalima]

@satazor I've just echoed SITE_URL in the failing step and the variable is indeed defined. Even when inlining https://next-with-moxy-pr-117.vercel.app, it fails.

[satazor]

Fixed it!