chore(js): Allow triggering release on external artifact static_viewer.html
#70
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, when a new version of static_viewer.html is released on the master of vtk-js we couldn't trigger a release because we do not commit this file but rather grab it during release.
This commit adds the hash of the latest version in a file and a hash check that runs during release but does not trigger a failure on a mismatch but rather a warning.
So now if static_viewer.html is updated on vtk-js:
.fetch_externals.sh
will just emit a warning.static_viewer.sha256
and trigger a new release on trame-vtk even if no othertrame-vtk
change happened during last release.cc: @jourdain