v0.7.0

Using Bzlmod (preferred)

1. Create a multitool.lock.json (schema)
2. Add to your MODULE.bazel file:

bazel_dep(name = "rules_multitool", version = "0.7.0")

multitool = use_extension("@rules_multitool//multitool:extension.bzl", "multitool")
multitool.hub(lockfile = "//:multitool.lock.json")
use_repo(multitool, "multitool")

Using WORKSPACE

1. Create a multitool.lock.json (schema)
2. Add to your WORKSPACE file:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "bazel_features",
    sha256 = "06f02b97b6badb3227df2141a4b4622272cdcd2951526f40a888ab5f43897f14",
    strip_prefix = "bazel_features-1.9.0",
    url = "https://github.com/bazel-contrib/bazel_features/releases/download/v1.9.0/bazel_features-v1.9.0.tar.gz",
)

http_archive(
    name = "rules_multitool",
    sha256 = "4e9647b7a49cac5c777febad09d454ce70265a50f987607831ce109b3a5d80e9",
    strip_prefix = "rules_multitool-0.7.0",
    url = "https://github.com/theoremlp/rules_multitool/releases/download/v0.7.0/rules_multitool-0.7.0.tar.gz",
)

load("@bazel_features//:deps.bzl", "bazel_features_deps")

bazel_features_deps()

load("@rules_multitool//multitool:multitool.bzl", "multitool")

multitool(
    name = "multitool",
    lockfile = "//:multitool.lock.json",
)

What's Changed

• Fix release automation script by @mark-thm in #25
• Document how to run tools on the command line by @alexeagle in #26
• Add convenience target for running in the current working directory by @mark-thm in #29

Full Changelog: v0.6.0...v0.7.0