[RELEASE] v0.0.1

.bcr/config.yml

@@ -1,6 +1,6 @@
 # See https://github.com/bazel-contrib/publish-to-bcr#a-note-on-release-automation
 # for guidance about whether to uncomment this section:
-#
-# fixedReleaser:
-#   login: my_github_handle
-#   email: me@my.org
+
+fixedReleaser:
+  login: hexdae
+  email: asnaghi@me.com

.bcr/presubmit.yml

@@ -1,5 +1,5 @@
 bcr_test_module:
-  module_path: "examples/bzlmod"
+  module_path: "examples/toolchain"
   matrix:
     platform: ["debian10", "macos", "ubuntu2004", "windows"]
     bazel: ["7.x", "6.x"]

.bcr/source.template.json

@@ -1,5 +1,5 @@
 {
   "integrity": "**leave this alone**",
-  "strip_prefix": "{REPO}_{VERSION}",
+  "strip_prefix": "{REPO}-{VERSION}",
   "url": "https://github.com/{OWNER}/{REPO}/releases/download/{TAG}/{REPO}_{TAG}.tar.gz"
 }

.github/workflows/release.yml

@@ -13,4 +13,4 @@ jobs:
   release:
     uses: bazel-contrib/.github/.github/workflows/release_ruleset.yaml@v6
     with:
-      release_files: toolchains_riscv_gnu_*.tar.gz
+      release_files: toolchains_riscv_gnu-*.tar.gz

.github/workflows/release_prep.sh

@@ -8,8 +8,8 @@ TAG=${GITHUB_REF_NAME}
 # The prefix is chosen to match what GitHub generates for source archives
 # This guarantees that users can easily switch from a released artifact to a source archive
 # with minimal differences in their code (e.g. strip_prefix remains the same)
-PREFIX="toolchains_riscv_gnu_${TAG:1}"
-ARCHIVE="toolchains_riscv_gnu_$TAG.tar.gz"
+PREFIX="toolchains_riscv_gnu-${TAG:1}"
+ARCHIVE="toolchains_riscv_gnu-$TAG.tar.gz"
 
 # NB: configuration for 'git archive' is in /.gitattributes
 git archive --format=tar --prefix=${PREFIX}/ ${TAG} | gzip > $ARCHIVE