close
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: bufbuild/rules_buf
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.5.1
Choose a base ref
...
head repository: bufbuild/rules_buf
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.5.2
Choose a head ref
  • 3 commits
  • 3 files changed
  • 3 contributors

Commits on Aug 8, 2025

  1. Add Publish to BCR workflow (#123)

    🤦
    jchadwick-buf
    jchadwick-buf authored Aug 8, 2025
    Configuration menu
    Copy the full SHA
    db56a74 View commit details
    Browse the repository at this point in the history

Commits on Aug 22, 2025

  1. Add s390x to list of supported cpu architecutres (#124)

    Buf added support for s390x in 1.56. I would like to add s390x support
    to rules_buf for this version or greater.
    jonathan-albrecht-ibm authored Aug 22, 2025
    Configuration menu
    Copy the full SHA
    8bdf33e View commit details
    Browse the repository at this point in the history
  2. Fix: pass in the repo root for the 'dir' argument (#119)

    In tools that run bazel commands from within `bazel run` the
    `BUILD_WORKSPACE_DIRECTORY` will be set and then in this
    [code](https://github.com/bazel-contrib/bazel-gazelle/blob/master/cmd/gazelle/fix-update.go#L122-L139)
    the directory will eventually be set to the top level repo root. An
    example of a tool that this can happen to is the
    [gopackagesdriver](https://github.com/bazel-contrib/rules_go/wiki/Editor-setup)
    in rules_go.
    
    This results in error messages like:
    ```
     no such package '@@rules_buf++buf+buf_deps//buf/validate': failed with code: 1, error: gazelle: .: not a subdirectory of repo root
    ```
    
    By passing in additional argument it explicitly sets the `dir` to the
    directory of the repo. Gazelle itself does something
    [similar](https://github.com/bazel-contrib/bazel-gazelle/blob/6803436a9c39209bd56ea1dba2dddda323a3c98b/internal/go_repository.bzl#L363)
    
    Co-authored-by: jchadwick-buf <116005195+jchadwick-buf@users.noreply.github.com>
    jgautier-dd and jchadwick-buf authored Aug 22, 2025
    Configuration menu
    Copy the full SHA
    a3128f1 View commit details
    Browse the repository at this point in the history
Loading