You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 14, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 14, 2026. It is now read-only.
I think we should bump the major version, and delete them, yes. The fields change still change on non-GA'd api's. The purpose of BOM's is to keep things working for users, not to mess w/ their world. @chingor13
Why? They should just use it directly, the tag should be BETA or ALPHA, so it will remind them it's not supported. We are very clear everywhere else, if you want, we can release an beta-bom, but I don't think it's a good idea.
Activity
danoscarmike commentedon Apr 13, 2020
@lesv what do you recommend? I'm assuming we can't just delete them from pom.xml?
lesv commentedon Apr 13, 2020
I think we should bump the major version, and delete them, yes. The fields change still change on non-GA'd api's. The purpose of BOM's is to keep things working for users, not to mess w/ their world.
@chingor13
chingor13 commentedon Apr 13, 2020
We still need a way to help users use clients that are not yet marked 1.0.0
lesv commentedon Apr 13, 2020
Why? They should just use it directly, the tag should be BETA or ALPHA, so it will remind them it's not supported. We are very clear everywhere else, if you want, we can release an beta-bom, but I don't think it's a good idea.
chingor13 commentedon Apr 13, 2020
@elharo We need to decide how we want to handle non 1.0 clients
chingor13 commentedon Apr 20, 2020
After some internal discussion, the plan is to:
google-cloud-bomsuztomo commentedon Dec 3, 2022
Update: We decided to include both GA and non-GA libraries in the BOM.