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: bazel-contrib/publish-to-bcr
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.2.1
Choose a base ref
...
head repository: bazel-contrib/publish-to-bcr
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.2.2
Choose a head ref
  • 4 commits
  • 4 files changed
  • 3 contributors

Commits on Jun 9, 2025

  1. Remediate zizmor template injection issues (#278)

    This is not an exhaustive set of fixes for zizmor
    reported issues, just those related to github inputs/vars
    and template injection
    
    Signed-off-by: Appu Goundan <[email protected]>
    loosebazooka authored Jun 9, 2025
    Configuration menu
    Copy the full SHA
    79e6de0 View commit details
    Browse the repository at this point in the history

Commits on Jun 10, 2025

  1. chore(deps): update toolchains_llvm (#181)

    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    renovate[bot] authored Jun 10, 2025
    Configuration menu
    Copy the full SHA
    e8be494 View commit details
    Browse the repository at this point in the history
  2. chore(deps): update dependency typescript to v5.8.2 (#221)

    Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
    renovate[bot] authored Jun 10, 2025
    Configuration menu
    Copy the full SHA
    e548280 View commit details
    Browse the repository at this point in the history

Commits on Jun 25, 2025

  1. Add author_{name,email} and committer_{name,email} Inputs (#279)

    We recently needed to change the `AUTHOR_NAME` and `AUTHOR_EMAIL` with which an internal bot triggers a PR to our BCR fork and therefore the commit that eventually lands to https://github.com/bazelbuild/bazel-central-registry 
    
    It probably makes sense to make these two inputs instead of hardcoded.
    jdsalaro authored Jun 25, 2025
    Configuration menu
    Copy the full SHA
    096e472 View commit details
    Browse the repository at this point in the history
Loading