Skip to content

Refetch version repositories when Bazel version changes#26

Merged
meteorcloudy merged 1 commit intobazel-contrib:mainfrom
fmeum:25-version
Nov 8, 2023
Merged

Refetch version repositories when Bazel version changes#26
meteorcloudy merged 1 commit intobazel-contrib:mainfrom
fmeum:25-version

Conversation

@fmeum
Copy link
Copy Markdown
Member

@fmeum fmeum commented Nov 8, 2023

Since every version change requires a server restart, it suffices to mark the version-dependent repos as local.

Fixes #25

Since every version change requires a server restart, it suffices to
mark the version-dependent repos as `local`.
@meteorcloudy
Copy link
Copy Markdown
Collaborator

This is brilliant! 😄 \o/

@meteorcloudy meteorcloudy merged commit 640a55a into bazel-contrib:main Nov 8, 2023
@fmeum fmeum deleted the 25-version branch November 8, 2023 15:13
@linzhp
Copy link
Copy Markdown

linzhp commented Nov 13, 2023

I ran into this issue today. Thanks for the fix!

github-merge-queue bot pushed a commit to bazel-contrib/rules_python that referenced this pull request Nov 14, 2023
Upgrade bazel_features to 1.1.1 to pick up a
[fix](bazel-contrib/bazel_features#26)
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

Successfully merging this pull request may close these issues.

version_repo is not updated when Bazel version changes

3 participants