You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: packages/components/RELEASE.md
+14-1
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,20 @@ Switch your local branch to `changeset-release/main`, open `packages/components/
21
21
22
22
Approve the 'Version Packages' PR (or request a review from [hashicorp/hds-engineering](https://github.com/orgs/hashicorp/teams/hds-engineering)) then merge it to `main`; this will publish the new package to npm automatically.
23
23
24
-
After the new version is published, don't forget to communicate the release and a summary of changes to the product teams.
24
+
After the new version is published, don't forget to communicate the release and a summary of changes to the product teams in the #team-design-systems and #tech-frontend channels.
25
+
26
+
### If you did not `alias` first
27
+
28
+
If you didn't alias the website URL before merging the Version Packages PR, here's what you do.
29
+
30
+
1. Follow steps 1-5 in the release process.
31
+
2. From your terminal, type `vercel redeploy hds-website-<deployment-id>-hashicorp.vercel.app`. This will re-deploy that preview, but with a new deployment id assigned.
32
+
3. Once that finishes, get the _new_ deployment id and run the `vercel alias` command as described in step 6.
33
+
34
+
Screenshot:
35
+
36
+

0 commit comments