Skip to content

docs: update stale bazel_dep versions in how-to guides #505

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.

Sign up for GitHub

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

Merged
AlexanderLanin merged 1 commit into from
Apr 21, 2026
Merged

docs: update stale bazel_dep versions in how-to guides #505

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/how-to/other_modules.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ A minimal example (add or extend the existing `bazel_deps` stanza):

.. code-block:: starlark

bazel_dep(name = "score_process", version = "1.3.0")
bazel_dep(name = "score_process", version = "1.5.3")

2) Extend your `docs` rule so Sphinx picks up the other module's inventory
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down
2 changes: 1 addition & 1 deletion docs/how-to/setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ designed to enhance documentation capabilities in S-CORE.
Add the module to your `MODULE.bazel` file:

```starlark
bazel_dep(name = "score_docs_as_code", version = "2.0.3")
bazel_dep(name = "score_docs_as_code", version = "4.0.1")
```

And make sure to also add the S-core Bazel registry to your `.bazelrc` file
Expand Down
Loading