Home

Welcome to the ui-components wiki!

master/jansa/ivanchuk/hammer

Release:

yarn
npm version patch
npm publish
git push upstream
git push upstream --tags
backport-ui-components.hammer 1.2.3  # the new version, https://github.com/himdel/dotfiles/tree/master/ManageIQ

Both Ops UI and Service UI will need a yarn add @manageiq/ui-components PR to use the new version. (Or yarn add @manageiq/ui-components@${THE_NEW_VERSION} if you want to be specific.)

hammer should use 1.1.*, ivanchuk 1.2.*, master(jansa) should use 1.3.*.

(For development, use yarn build ; yarn link in ui-components, and yarn link @manageiq/ui-components in ui-classic/service. yarn unlink @manageiq/ui-components ; yarn when done)

gaprindashvili

Backport:

git cherry-pick -x -m1 $MERGE_COMMIT_SHA

(and add a comment to the PR, remove gaprindashvili/yes and add gaprindashvili/backported)

Release:

https://github.com/ManageIQ/ui-components/wiki/Releasing-a-new-version#releasing-both-npm--bower

Make ops & sui use the new release:

https://github.com/ManageIQ/ui-components/wiki/Getting-UI-components-updates-backported-to-Gaprindashvili

Gaprindashvili will only work with the 1.0.* series, not older, not newer.

fine

Pretty much the same as gaprindashvili, except it's the 0.0.* series, and there's no branch since we didn't have to backport yet.

Should be theoretically possible, the Ops UI will pick up the changes without a PR (SUI, will be the same as in gaprindashvili).

More differences in the older versions are described in https://github.com/ManageIQ/ui-components/wiki/Updating-ui-components-on-an-appliance