bazel version fails with custom flags

[SpencerC]

Description of the bug:

If a developer sets common settings in their .bazelrc file that include custom flags, bazel version comes back with "ERROR: Unrecognized arguments: ...".

Which category does this issue belong to?

CLI

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Add a custom flag somewhere in your workspace:

load("@bazel_skylib//rules:common_settings.bzl", "string_flag")

string_flag(
    name = "someflag",
    build_setting_default = "somevalue",
    visibility = ["//visibility:public"],
)

Add the following line to your .bazelrc file:

common --//backend:project_id=ggx-prototype

Run
bazel version

Which operating system are you running Bazel on?

macOS

What is the output of bazel info release?

release 6.2.1

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?

No response

Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

[Wyverald]

This is fixed in 6.4.0 (see #18130 (comment)). Please upgrade.