Skip to content

Have a new release for stardoc #109

@meteorcloudy

Description

@meteorcloudy

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 bazelbuild/bazel-central-registry#7

Please have a new stardoc release.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions