fix(core): delete duplicate select component

[jorgemoya]

What/Why?

SelectField was wrapping the Select component and causing double label/errors to be displayed. Deletes SelectField in favor of Select.

Added the workaround for the Radix issue to the Select component. Confirmed issue is not resolved.

Testing

Before:

After:

Migration

Remove SelectField and update components to use Select instead.

[changeset-bot]

🦋 Changeset detected

Latest commit: ea5f21b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@bigcommerce/catalyst-core	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
catalyst	Ready	Preview, Comment	Jan 7, 2026 6:23pm

[chanceaclark]

I fully forget why we did it, but I remember having two "Selects" was intentional based on this PR #2326 Do we want to keep the two still or does it make sense to deduplicate based on that PR?

[jorgemoya]

I fully forget why we did it, but I remember having two "Selects" was intentional based on this PR #2326 Do we want to keep the two still or does it make sense to deduplicate based on that PR?

Good callout @chanceaclark. I can't see a reason to separate these, maybe @hunterbecton can provide some context.

[jorgemoya]

@chanceaclark I just noticed that at some point, the Select primitive component was modified to include a label, thus making the SelectField component obsolete.

We can keep just one (Select), or if we want to keep them separate, we need to make the Select component act as a true primitive with no label or error message logic.

[chanceaclark]

I believe the SelectField contains the input, but I think there are some UI's like the PDP that utilize Select so moving over to utilizing an component with an input breaks when trying to add to the cart. I would double check though. @hunterbecton might know more though.

[jorgemoya]

I believe the SelectField contains the input, but I think there are some UI's like the PDP that utilize Select so moving over to utilizing an component with an input breaks when trying to add to the cart. I would double check though. @hunterbecton might know more though.

SelectField contains Select, which is the original problem, since both included a label and errors.

With the removal of SelectField, I have tested all UIs that use the Select component and see no issues.

[hunterbecton]

I believe the SelectField contains the input, but I think there are some UI's like the PDP that utilize Select so moving over to utilizing an component with an input breaks when trying to add to the cart. I would double check though. @hunterbecton might know more though.

SelectField contains Select, which is the original problem, since both included a label and errors.

With the removal of SelectField, I have tested all UIs that use the Select component and see no issues.

I don't recall why we have a separate SelectField, but I'm introducing a Field component in storefront-kit so we don't need one-off components that might need labels, input descriptions, or field errors.

[hunterbecton]

I don't see an issue with dropping the SelectField