-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tag the upstream deephaven-base-images after release #1676
Comments
mofojed
added a commit
that referenced
this issue
Dec 22, 2023
Release notes https://github.com/deephaven/web-client-ui/releases/tag/v0.58.0 ### Bug Fixes * `figure_title` and `chart_title` were not mapped up correctly ([#1676](deephaven/web-client-ui#1676)) ([73e0b65](deephaven/web-client-ui@73e0b65)), closes [#1674](deephaven/web-client-ui#1674) [#1675](deephaven/web-client-ui#1675) ### Features * "Group" column for rollup/tree tables ([#1636](deephaven/web-client-ui#1636)) ([ba1d51b](deephaven/web-client-ui@ba1d51b)), closes [#1555](deephaven/web-client-ui#1555) * Add alt+click shortcut to copy cell and column headers ([#1694](deephaven/web-client-ui#1694)) ([4a8a81a](deephaven/web-client-ui@4a8a81a)), closes [deephaven/web-client-ui#1585](deephaven/web-client-ui#1585) * Theming - Spectrum variable mapping and light theme ([#1680](deephaven/web-client-ui#1680)) ([2278697](deephaven/web-client-ui@2278697)), closes [#1669](deephaven/web-client-ui#1669) [#1539](deephaven/web-client-ui#1539) --------- Co-authored-by: deephaven-internal <deephaven-internal@users.noreply.github.com> Co-authored-by: mikebender <mikebender@deephaven.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We'd like to tag the deephaven-base-images after deephaven-core releases. There is no good way to do this with plain docker tooling afaict.
https://github.com/google/go-containerregistry/tree/main/cmd/crane seems like a reasonable approach, and I've tested it out successfully.
The text was updated successfully, but these errors were encountered: