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.

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

Jump to bottom

[6.4.0] MODULE.bazel.lock file contains user specific paths #19698

Merged
merged 2 commits into from
Oct 2, 2023
Merged

[6.4.0] MODULE.bazel.lock file contains user specific paths #19698

merged 2 commits into from
Oct 2, 2023

Commits on Oct 2, 2023

  1. Remove user specific absolute path from lockfile 

    - Store the unresolved registry string "containing %workspace% placeholder" in IndexRegistry and use it to create the remote_patches
- Later when creating the repo rule, resolve the registry path in remote_patches

fixes bazelbuild#19621

PiperOrigin-RevId: 570028910
Change-Id: I984c6b7494fb377bcf8b3568fa98c740c8618c33
    @SalmaSamy @bazel-io
    SalmaSamy authored and bazel-io committed Oct 2, 2023
    Configuration menu
    Copy the full SHA
    795cd82 View commit details
    Browse the repository at this point in the history

  2. Merge branch 'release-6.4.0' into cp19621-6.4.0

    @meteorcloudy
    meteorcloudy committed Oct 2, 2023
    Configuration menu
    Copy the full SHA
    09d9f56 View commit details
    Browse the repository at this point in the history