Latest behind available versions

Describe the bug Has anyone ever seen or might know why the dist-tag or latest is behind a patch version of what’s available?

We use a tool called changesets to determine when to publish a package, and since the version is behind, our package.json is set at 3.0.7, but npm dist-tag is returning 3.0.6 even though 3.0.7 is in Verdaccio, just not set as latest.

FROM verdaccio/verdaccio:4.0.1
ENV PORT=80
USER root
RUN npm install && \
  test -d node_modules
RUN npm install \
  verdaccio-htpasswd \
  verdaccio-s3-storage
COPY logo-white.png .
COPY config.yaml /verdaccio/conf/config.yaml
COPY htpasswd.txt /verdaccio/conf/htpasswd

We’re using Kubernetes with 3 replicas.

[aphix]

@juanpicado Will do; haven’t needed to publish since but I’ll make sure to record versions & steps next time I do in the off-chance it fails.

Unfortunately that publish was automated via a CI running in the office and everyone is working from home due to COVID so I have even less ability to inspect than normal. Thanks.

FWIW, manually updating the tag worked fine (via npm dist-tag) as a workaround.

[jonathancreamer-eb]

Thanks, no problem.