Implemented solution: The version has been updated in the CLOUDHARNESS_FRONTEND_BUILD image, which should be used a a dependency to build other node applications.
How to test this PR: Automated tests are enough here as the some images won't build if the image is not found
Sanity checks:
[x] The pull request is explicitly linked to the relevant issue(s)
[x] The issue is well described: clearly states the problem and the general proposed solution(s)
[x] From the issue and the current PR it is explicitly stated how to test the current change
[x] The labels in the issue set the scope and the type of issue (bug, feature, etc.)
[ ] All the automated test checks are passing
[ ] All the linked issues are included in one milestone
[ ] All the linked issues are in the Review state
[ ] All the linked issues are assigned
Breaking changes (select one):
[ ] The present changes do not change the preexisting api in any way
[x] This PR and the issue are tagged as a breaking-change
Possible deployment updates issues (select one):
[x] There is no reason why deployments based on CloudHarness may break after the current update
[ ] This PR and the issue are tagged as alert:deployment
Test coverage (select one):
[x] Tests for the relevant cases are included in this pr
[ ] The changes included in this pr are out of the current test coverage scope
Documentation (select one):
[ ] The documentation has been updated to match the current changes
[x] The changes included in this PR are out of the current documentation scope
Closes CH-118
Implemented solution: The version has been updated in the CLOUDHARNESS_FRONTEND_BUILD image, which should be used a a dependency to build other node applications.
How to test this PR: Automated tests are enough here as the some images won't build if the image is not found
Sanity checks:
Breaking changes (select one):
breaking-changePossible deployment updates issues (select one):
alert:deploymentTest coverage (select one):
Documentation (select one):
Nice to have (if relevant):