Skip to content
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

Bazel 8.1.0 will fix the filename double-encoding issue mentioned in docs/generate.py #818

Closed
gutron opened this issue Jan 24, 2025 · 0 comments
Assignees

Comments

@gutron
Copy link
Collaborator

gutron commented Jan 24, 2025

Specifically, the work-around in the _markdown function will no longer be needed starting with Bazel 8.1.0. I'm not sure how that should be handled here since the code usually supports multiple versions of Bazel.

@phst phst self-assigned this Jan 26, 2025
phst added a commit to phst/bazel_features that referenced this issue Jan 26, 2025
bazelbuild/bazel#24935 changes the observable behavior
of starlark_doc_extract, and consumers need to adapt.

Work towards bazelbuild/bazel#374
Work towards phst/rules_elisp#818
phst added a commit to phst/bazel_features that referenced this issue Jan 28, 2025
bazelbuild/bazel#24935 changes the observable behavior
of starlark_doc_extract, and consumers need to adapt.

Work towards bazelbuild/bazel#374
Work towards phst/rules_elisp#818
fmeum pushed a commit to bazel-contrib/bazel_features that referenced this issue Jan 28, 2025
bazelbuild/bazel#24935 changes the observable
behavior of starlark_doc_extract, and consumers need to adapt.

Work towards bazelbuild/bazel#374
Work towards phst/rules_elisp#818
@phst phst closed this as completed in 2489227 Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants