Closed meteorcloudy closed 3 years ago
The last release for stardoc is still in 2019, and Bazel itself uses a commit that's newer than that release. Ideally we don't want downstream users to pin point a certain un-verified commit.
This is also blocking https://github.com/bazelbuild/bazel-central-registry/issues/7
Please have a new stardoc release.
/cc @c-parsons
Will release a new version as soon as we add a proper way to generate a release tarball: https://github.com/bazelbuild/stardoc/pull/111
Released https://github.com/bazelbuild/stardoc/releases/tag/0.5.0
The last release for stardoc is still in 2019, and Bazel itself uses a commit that's newer than that release. Ideally we don't want downstream users to pin point a certain un-verified commit.
This is also blocking https://github.com/bazelbuild/bazel-central-registry/issues/7
Please have a new stardoc release.