Closed shawnbot closed 3 years ago
This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.
đ Inspect: https://vercel.com/sfds/formio-sfds/rep4k3ev2
â
Preview: https://formio-sfds-git-vercel-alias-version.sfds.vercel.app
Size Change: +5.87 kB (6%) đ
Total Size: 92 kB
Filename | Size | Change | |
---|---|---|---|
dist/examples.js |
3.51 kB | +320 B (9%) | đ |
dist/formio-sfds.css |
14 kB | -14 B (0%) | |
dist/formio-sfds.standalone.js |
68.1 kB | +5.57 kB (8%) | đ |
dist/portal.js |
5.36 kB | -10 B (0%) |
This adds an "alias" workflow that creates a Vercel deployment URL alias whenever a tag beginning with
v
is created. For instance, when we tag the next major release withv7.0.0
, the workflow should run and create an alias fromformio-sfds-v7-0-0.vercel.app
to the current production deployment.The point of this is to make it easier to compare rendered examples in different versions of our theme.
In the future, these aliases could also power a dropdown on the site that allows you to see the examples and docs as of a specific version by changing the hostname of the current URL. I'm going to manually add aliases for a few recent versions by going down the production deployments list. I don't think there's any need to automate doing the retroactive aliases for versions earlier than, say, 6.3.0.