Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/bazel-contrib/rules_distroless/compare/v0.3.8...v0.3.9 below:

Comparing v0.3.8...v0.3.9 · bazel-contrib/rules_distroless · GitHub

• Pricing

Failed to load repositories. Confirm that selected base ref is valid, then try again.

Loading

Failed to load repositories. Confirm that selected head ref is valid, then try again.

Loading

• 13 commits
• 55 files changed
• 5 contributors

1. Configuration menu Browse the repository at this point in the history
2. Configuration menu Browse the repository at this point in the history

3. fix: e2e MODULE.bazel.lock conflicts and repo name in copy.sh script (#…

   …87)
   
   * fix: MODULE.bazel.lock conflicts
   
   See bazelbuild/bazel#20369
   
   While working on refactoring, I kept hitting rebase conflicts due to
   issues with the MODULE lock. I guess it's because the Bazel version in
   e2e tests is much lower than the current one with the fix (7.2) but
   still, I don't think it adds much to have the lock in e2e testing.
   
   * fix: repo name in copy.sh script
   
   PR #73 added the `_resolve` and this breaks the buildozer fix / autofix
   
   * fix: remove dead locks
   
   It seemed like 75afff9 in #47 added the new locks but as new files, that
   is, the old ones were left behind.

   Configuration menu Browse the repository at this point in the history
4. Configuration menu Browse the repository at this point in the history

5. tar: make all gzip compression hermetic (#75)

   We weren't passing the flag to make gzip hermetic. Without the flag to
   ignore timestamp, the shasum will differ based on the system time.
   
   Also, DEFAULT_ARGS contained "--options=gzip:...", which is invalid when
   using any other compression scheme. Therefore, remove that option from
   DEFAULT_ARGS and provide an alternate function called
   `add_default_compression_args` to add per-compression type default
   arguments which can do things like make the compression more hermetic.

   Configuration menu Browse the repository at this point in the history

6. feat: add MODULE.bazel support to copy.sh plus silent lockless repos (#…

   …88)
   
   * feat: add support for MODULE.bazel to the lock copy.sh script
   
   Add support for MODULE.bazel to the lock script and avoid printing an
   unnecessary (and annoying 😅) error when building in a "modern repo".
   
   * feat: avoid DEBUG messages for lockless repos
   
   Add a `nolock` attribute to avoid getting annoying DEBUG messages for
   repos that we explicitly want to run without a lock.

   Configuration menu Browse the repository at this point in the history

1. Configuration menu Browse the repository at this point in the history

1. Configuration menu Browse the repository at this point in the history

2. refactor: improve the lock copy.sh script (#92)

   * separate the script into a template file so it's easier to shellcheck
     and syntax highlight in editors.
   
   * shellcheck the script and remove all SC2086 warnings
     ("Double quote to prevent globbing and word splitting")
   
   * improve the buildozer help messages in the copy.sh script:
     * reduce duplication of buildozer command
     * add a more clear autofix bazel run command that can be easily
       copy-pasted
   
   * change some of the variable names in the copy.sh template for longer,
     easier to understand names (repo_name >> name, lock_label >> label)
   
   * move repo_name and workspace_relative_path into variables to reduce
     line length and improve readability

   Configuration menu Browse the repository at this point in the history

1. Configuration menu Browse the repository at this point in the history

1. docs: improve documentation (#109)

   * chore: ignore MODULE.bazel.lock
   
   27242f4 pushed lock version to `12` (my guess is Bazel 8?) plus other
   changes that e.g. don't match running with `.bazelversion`'s `7.3.1`.
   
   Regardless, the `MODULE.bazel.lock` file is still not stable and e.g.
   just running it in another operating system causes things to change...
   so let's just ignore it like I did for the `e2e` tests in 70c14c0
   
   * docs: README.md
   
   Revamp README adding an improved version of the Bzlmod and `WORKSPACE`
   snippets that are available in the release page.
   
   IMHO the release page should now remove those snippets and point to the
   README.
   
   * docs: revamp apt.macro doc and create apt/extensions doc
   
   Split the Bzlmod / `WORKSPACE` docs from `apt.install` macro and remove
   a bunch of old references. Also mark it all as legacy since the present
   and future is all Bzlmod.
   
   Create apt/extensions docs.
   
   Add a whole common section to both docs with (hopefully :)
   easy-to-follow documentation inspired by my answer to a Slack question
   (https://bazelbuild.slack.com/archives/CA3NW13MH/p1729804678924819).

   Configuration menu Browse the repository at this point in the history

1. Configuration menu Browse the repository at this point in the history
2. Configuration menu Browse the repository at this point in the history

Loading

Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.

You can try running this command locally to see the comparison on your machine:
git diff v0.3.8...v0.3.9

You can’t perform that action at this time.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4