Skip to content

Commit e4cf01a

Browse files
authored
Merge pull request #2195 from hashicorp/melsumner/update-release
Update RELEASE.md to include `redeploy` info
2 parents eb3f886 + 6d5f0f0 commit e4cf01a

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

packages/components/RELEASE.md

+14-1
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,20 @@ Switch your local branch to `changeset-release/main`, open `packages/components/
2121

2222
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.
2323

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+
![Terminal view of steps described previously in this document](https://github.com/hashicorp/design-system/assets/4587451/d69abce7-2741-4e1a-834d-f5367436c6da)
37+
2538

2639
## Local testing of versioning
2740

0 commit comments

Comments
 (0)