BCR 1.1.0 release doesn't seem to point to 1.1.0

[oliverlee]

I tried to update to 1.1.0 with:

bazel_dep(
    name = "toolchains_arm_gnu",
    version = "1.1.0",
    dev_dependency = True,
)

but it doesn't seem to actually use 1.1.0. For example, additional_link_libraries is not available.

When I checked the release tarball, it looks the contents are using an older version of the source as well.

[hexdae]

this is really odd, let me take a look

[oliverlee]

The release workflow used commit dde4ecc
https://github.com/hexdae/toolchains_arm_gnu/actions/workflows/release.yml

No idea why though.

[hexdae]

Maybe I mistakenly tagged an old commit, one sec, user error, let me release again

[hexdae]

No I think the tag is on the right commit, very odd

commit 96bd0b4f1eb7d01bf5df3da769517a9716db5cf5 (HEAD -> master, tag: v1.1.0, origin/master, origin/HEAD)
Author: Oliver Lee <oliverzlee@gmail.com>
Date:   Sun Jul 6 13:53:16 2025 -0700

    allow toolchains to always link specific libraries (#71)

    * allow toolchains to always link specific libraries

    Define toolchain attribute `additional_link_libraries` which specifies
    libraries that are always linked to an executable. This can be used to
    associate specific libraries (e.g. startup code, periph IO) to a
    toolchain, removing the need to specify `deps` with `select` when
    working with multiple toolchains.

    When defining a toolchain, a bootstrap toolchain is created if
    `additional_link_libraries` is not empty. This bootstrap toolchain is
    used to build all the targets in `additional_link_libraries` and these
    built libraries are added as a dependency of the primary toolchain.

    * refactor cortex-m examples

    * add test with -Wpedantic