Setup v3 hosting strategy for both ui-kit and design-system
💬 Description
Ic-ui-kit
· Version 2 is released as normal, when merged into main.
· Version 3 workflow to be added to automatically deploy a pre-release flagged version to npm, that won’t automatically be installed with a npm install (make sure to confirm/test that it will not be installed automatically and will be ignored).
Ic-design-system
· Version 2 is released as normal, when merged into main.
· Version 3 is to be hosted in the same way feature branches are now (no workflow changes needed), so we have a temporary URL, that is constant and with v3 in the URL
· Designers to design how they want us to be able to switch between the old version 2 and version 3, when that time comes. I think we start with only having the most up to date version of version 2 and version 3, not any minor versions between, this will increase our deployment sizes drastically, and not something anybody has requested yet.
MI6-255
commented
4 months ago
Summary
Setup v3 hosting strategy for both ui-kit and design-system
💬 Description
Ic-ui-kit · Version 2 is released as normal, when merged into
main. · Version 3 workflow to be added to automatically deploy a pre-release flagged version to npm, that won’t automatically be installed with a npm install (make sure to confirm/test that it will not be installed automatically and will be ignored). Ic-design-system · Version 2 is released as normal, when merged intomain. · Version 3 is to be hosted in the same way feature branches are now (no workflow changes needed), so we have a temporary URL, that is constant and with v3 in the URL · Designers to design how they want us to be able to switch between the old version 2 and version 3, when that time comes. I think we start with only having the most up to date version of version 2 and version 3, not any minor versions between, this will increase our deployment sizes drastically, and not something anybody has requested yet.💰 Use value
To be able to start work on v3.