fix: avoid using deprecated ctx.resolve_tools

[tjgq]

See bazelbuild/bazel#22249 for context.

Fixes #458.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[meteorcloudy]

@sgammon Are we getting a new release anytime soon? For now, Bazel has to patch rules_graalvm to make sure we can upgrade to Bazel 8: https://github.com/bazelbuild/bazel/blob/aa397cf37d7d013740b4081c19bef38b992b3eab/MODULE.bazel#L64-L69, other users probably have to do the same.

[sgammon]

@meteorcloudy IIRC release couldn't happen last time it was attempted (at least at the latest version of GraalVM) because of unstable download URLs. those may have been fixed now, so it's worth a retry.

is the patch above applied because there hasn't been a release to BCR, or because there hasn't been a release in general? If it's sufficient to release to the GH repo only, that can be very quick

[meteorcloudy]

because of unstable download URLs.

We can skip this check on BCR presubmit.

is the patch above applied because there hasn't been a release to BCR

Yes, ideally there should be a new version on BCR containing this fix.

[meteorcloudy]

See the same breakage of rules_graalvm in bazelbuild/bazel-central-registry#3260

[sgammon]

@meteorcloudy In this case the unstable download URLs were GraalVM's own URLs... unless that's what you mean? I do think they have likely fixed them now (we needed at least one 23.x point-release so that the archive URLs exist, and I believe that has taken place).

I'm out for the holiday today but I can take this on once I'm back (probably Sun or Mon). Thanks for your patience and for explaining.

[meteorcloudy]

No worries, Bazel itself is fine for now, I'm just worried other rules_graalvm might hit this after Bazel 8 release (which will happen next week). Thanks for taking a look!