Skip to content

[pull] main from bazel-contrib:main#369

Merged
pull[bot] merged 1 commit into
garymm:mainfrom
bazel-contrib:main
Aug 17, 2025
Merged

[pull] main from bazel-contrib:main#369
pull[bot] merged 1 commit into
garymm:mainfrom
bazel-contrib:main

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented Aug 17, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.3)

Can you help keep this open source service alive? 💖 Please sponsor : )

After merging #3058, I wanted to try creating a `universal` requirements
file for our `sphinx` setup and have an integration test in that way. It
seems that `alabaster` has different versions for different python
versions and we were not handling this correctly. In #3058 I have
attempted adding a unit test for this but it escaped me that the only
time where this bug manifests itself is when the `parse_requirements` is
used multiple times, once per each `python_version`.

With this I think it is safe to say that the #2797 is fixed, because we
found a bug, where we were not skipping requirements.

As an added counter measure, I have added an extra check elsewhere to
catch a regression.

Fixes #2797
@pull pull Bot locked and limited conversation to collaborators Aug 17, 2025
@pull pull Bot added the ⤵️ pull label Aug 17, 2025
@pull pull Bot merged commit 5e75007 into garymm:main Aug 17, 2025
1 check passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant