From ee3326b792d17c116b7b8977e5187415372e4221 Mon Sep 17 00:00:00 2001
From: Fabian Meumertzheim <fabian@meumertzhe.im>
Date: Sat, 9 Dec 2023 15:29:14 +0100
Subject: [PATCH] Update buildozer to 6.4.0 (#1)

---
 MODULE.bazel | 12 ++++++------
 README.md    |  6 +++---
 2 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/MODULE.bazel b/MODULE.bazel
index cd14268..0a4e272 100644
--- a/MODULE.bazel
+++ b/MODULE.bazel
@@ -1,17 +1,17 @@
 module(
     name = "buildozer",
-    version = "6.3.3",
+    version = "6.4.0",
     bazel_compatibility = [">=6.2.0"],
 )
 
 buildozer_binary = use_extension("//:buildozer_binary.bzl", "buildozer_binary")
 buildozer_binary.buildozer(
     sha256 = {
-        "darwin-amd64": "9b0bbecb3745250e5ad5a9c36da456699cb55e52999451c3c74047d2b1f0085f",
-        "darwin-arm64": "085928dd4deffa1a7fd38c66c4475e37326b2d4942408e8e3d993953ae4c626c",
-        "linux-amd64": "1dcdc668d7c775e5bca2d43ac37e036468ca4d139a78fe48ae207d41411c5100",
-        "linux-arm64": "94b96d6a3c52d6ef416f0eb96c8a9fe7f6a0757f0458cc8cf190dfc4a5c2d8e7",
-        "windows-amd64": "fc1c4f5de391ec6d66f2119c5bd6131d572ae35e92ddffe720e42b619ab158e0",
+        "darwin-amd64": "d29e347ecd6b5673d72cb1a8de05bf1b06178dd229ff5eb67fad5100c840cc8e",
+        "darwin-arm64": "9b9e71bdbec5e7223871e913b65d12f6d8fa026684daf991f00e52ed36a6978d",
+        "linux-amd64": "8dfd6345da4e9042daa738d7fdf34f699c5dfce4632f7207956fceedd8494119",
+        "linux-arm64": "6559558fded658c8fa7432a9d011f7c4dcbac6b738feae73d2d5c352e5f605fa",
+        "windows-amd64": "e7f05bf847f7c3689dd28926460ce6e1097ae97380ac8e6ae7147b7b706ba19b",
     },
 )
 use_repo(buildozer_binary, "buildozer_binary")
diff --git a/README.md b/README.md
index 26132f1..f0dcb6c 100644
--- a/README.md
+++ b/README.md
@@ -11,7 +11,7 @@ This Bazel module provides a pinned, prebuilt version of [buildozer](https://git
 1. Add the following line to your `MODULE.bazel` file:
 
 ```starlark
-bazel_dep(name = "buildozer", version = "6.3.3", dev_dependency = True)
+bazel_dep(name = "buildozer", version = "6.4.0", dev_dependency = True)
 ```
 
 2. Run buildozer via `bazel run`:
@@ -29,7 +29,7 @@ You can also use buildozer in a repository rule or module extension, i.e., durin
 1. Add the following line to your `MODULE.bazel` file:
 
 ```starlark
-bazel_dep(name = "buildozer", version = "6.3.3")
+bazel_dep(name = "buildozer", version = "6.4.0")
 ``````
 
 2. In your repository rule or module extension implementation function, get the path to the buildozer binary as follows:
@@ -54,7 +54,7 @@ If you dont want to or can't `load` from `@buildozer`, you can also use the foll
 1. Add the following lines to your `MODULE.bazel` file:
 
 ```starlark
-bazel_dep(name = "buildozer", version = "6.3.3")
+bazel_dep(name = "buildozer", version = "6.4.0")
 
 buildozer_binary = use_extension("@buildozer//:buildozer_binary.bzl", "buildozer_binary")
 use_repo(buildozer_binary, "buildozer_binary")