fix(select): return single value for single select

[AykutSarac]

fixes #675

[muratcorlu]

Do you think we should make a major release (v3) for this?

[AykutSarac]

I believe we should at least have one new component per major release or significant change, until that time such changes can wait unless it requires urgent fix.

[muratcorlu]

Stable releases should last longer than a few months. Our consumers should not need to make a careful upgrade every few months. So I propose avoiding breaking changes as much as possible for a while, and collect those proposals in a backlog for a bigger major release.

We may consider to have another branch for major releases like next-major and we can merge breaking changes to that branch, but this will also add extra maintenance cost since we will need to sync other works from next branch to next-major continuously.

[AykutSarac]

I think beta releases may contain breaking changes, after all they're neither minor or major release. We can note the list of breaking changes at the major release when it's out.

[muratcorlu]

Yes, beta releases can have major releases. But we currently have only a single beta channel. If we merge this branch with a "breaking change" notice in commit message, then our next branch will release "v3.0.0-beta.1". Then when we merge next to main, we'll have a major stable release. there will be no chance to make a "v2.3.0" release.

[github-actions]

🎉 This PR is included in version 2.4.0-beta.9 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 3.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀