bazelbuild / bazelbuild/bazelisk

Have a way to mark Bazel releases as bad and ignore them

Open
#243 0 comments 0 reactions 0 assignees View on GitHub
P2 type: feature request
Dominant language
Go
Stars
2.7k
Forks
424
PR merge metrics
No merged PRs in 30d

Description

This of course shouldn't apply when the Bazel release is requested explicitly.

The need for this came up in the discussion of https://github.com/bazelbuild/bazel/issues/13502. Fortunately, Philipp came up with a fix quickly but having this feature would have given us more time if we would have needed it.

Contributor guide

Open the contributing guide

Research direction

Start by tracing how Bazelisk selects Bazel releases and handles explicitly requested versions. Read the discussion in bazelbuild/bazel#13502 for the motivation, then define how a bad release would be recorded, ignored during normal selection, and still honored when explicitly requested.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.