When we publish a patch version of deephaven-core (and subsequently a patch version of the @deephaven/jsapi-types package), it should not be labelled as latest.
For example, we previously published v0.34.3, which is the latest version. We then went back and released a patch to v0.33, and published v0.33.4. That should not have the dist-tag of latest, latest should still point to v0.34.3.
For web-client-ui packages, we set the dist tag to just the major version number of the release branch that is being patched, e.g. https://github.com/deephaven/web-client-ui/blob/37571633dd0be5b7a606bee45af10f6a7d09d4ec/lerna.json#L6
See screenshot below. v0.34.3 was published 13 days ago, and then we published a patch 0.33.4 yesterday, but that stole the latest tag.
Description
When we publish a patch version of deephaven-core (and subsequently a patch version of the
@deephaven/jsapi-types
package), it should not be labelled aslatest
. For example, we previously publishedv0.34.3
, which is thelatest
version. We then went back and released a patch to v0.33, and publishedv0.33.4
. That should not have the dist-tag oflatest
,latest
should still point tov0.34.3
. For web-client-ui packages, we set the dist tag to just the major version number of the release branch that is being patched, e.g. https://github.com/deephaven/web-client-ui/blob/37571633dd0be5b7a606bee45af10f6a7d09d4ec/lerna.json#L6See screenshot below. v0.34.3 was published 13 days ago, and then we published a patch 0.33.4 yesterday, but that stole the
latest
tag.Additional details and attachments![image](https://github.com/deephaven/deephaven-core/assets/4505624/79c403ae-d143-4c99-bea7-97982e75611c)