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

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

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

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

• 4 commits
• 20 files changed
• 3 contributors

1. fix: target_compatible_with excluding arm64 (#84)

   * fix: target_compatible_with excluding arm64
   
   The 'ci: update ci and exclude windows' commit added
   'target_compatible_with' arguments to some of the tests restricting them
   to linux but it also forced amd64 instead of allowing the tests to run
   in both linux/amd64 and linux/arm64.
   
   Before this fix, I would get SKIPPED tests when testing on linux/arm64
   and now all the tests run.
   
   * chore: updating locks
   
   Just doing 'bazel run' on the locks (except apt_security which is
   lock-less) and runnign the tests for linux/amd64 and linux/arm64:
   
   ```
   bazel run @bullseye//:lock
   bazel run @shared_dependencies//:lock
   bazel run @noble//:lock
   
   bazel test //...
   ```
   
   produces these changes, which seem to be, mostly,
   
   * tabs vs 2 spaces in lock.json
   * keys with '_' instead of '~'
   * some tooling in MODULES.lock

   Configuration menu Browse the repository at this point in the history

2. feat: support multiple components (#85)

   * fix: target_compatible_with excluding arm64
   
   The 'ci: update ci and exclude windows' commit added
   'target_compatible_with' arguments to some of the tests restricting them
   to linux but it also forced amd64 instead of allowing the tests to run
   in both linux/amd64 and linux/arm64.
   
   Before this fix, I would get SKIPPED tests when testing on linux/arm64
   and now all the tests run.
   
   * chore: updating locks
   
   Just doing 'bazel run' on the locks (except apt_security which is
   lock-less) and runnign the tests for linux/amd64 and linux/arm64:
   
   ```
   bazel run @bullseye//:lock
   bazel run @shared_dependencies//:lock
   bazel run @noble//:lock
   
   bazel test //...
   ```
   
   produces these changes, which seem to be, mostly,
   
   * tabs vs 2 spaces in lock.json
   * keys with '_' instead of '~'
   * some tooling in MODULES.lock
   
   * feat: Support multiple components
   
   Add support for multiple sources.list components (e.g. "main contrib").
   
   Before, all of the components were being parsed as one string which
   resulted in _fetch_package_index() failing.
   
   See https://wiki.debian.org/SourcesList#sources.list_format and
   https://wiki.debian.org/DebianRepository/Format#Components
   
   ---------
   
   Co-authored-by: Sahin Yort <thesayyn@gmail.com>

   Configuration menu Browse the repository at this point in the history

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

2. fix: Debian packages with tar.gz data file (#99)

   When a Debian package has a data file that's already compressed with gz
   and named data.tar.gz it fails with Error in genrule: rule 'data' has
   file 'data.tar.gz' as both an input and an output.
   
   See issue #98

   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.7...v0.3.8

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