Skip to content

Conversation

@ChristosT
Copy link
Contributor

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:

  • If we do not care .fetch_externals.sh will just emit a warning
  • If we do care we update .static_viewer.sha256 and trigger a new release on trame-vtk even if no other trame-vtk change happened during last release.

cc: @jourdain

…r.html

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:
- If we do not care `.fetch_externals.sh` will just emit a warning
- If we **do** care we update .static_viewer.sha256 and trigger a new release
  on trame-vtk even if no other `trame-vtk` change happened during last
  release.
@jourdain jourdain merged commit eb8461a into Kitware:master May 6, 2024
ChristosT added a commit to ChristosT/trame-vtk that referenced this pull request May 6, 2024
Similar to offline_viewer.html we track and report mismatched hash
of all external dependencies.
see also Kitware#70
jourdain pushed a commit that referenced this pull request May 6, 2024
Similar to offline_viewer.html we track and report mismatched hash
of all external dependencies.
see also #70
@ChristosT ChristosT deleted the add-way-to-trigger-on-viewer-static-viewer branch May 6, 2024 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants