Khurram

I think we should do a release of v0.5.0 with v1. I would raise the pr. on Monday. v1 has been out for a while and now it doesn't make...

@adambkaplan We decided to do a release based on v1beta1 APIs in the WG call. Afterward, we would upgrade.

CLI should have LTS for v1beta1 pipelines, @tektoncd/cli-maintainers can confirm. @tektoncd/chains-maintainers can clarify whether we would have lts release for Pipelines v1beta1 and chains. Results is still alpha project. So...

v1beta1 is now deprecated. Previously, annotations were used to transfer information during conversion. @vdemeester, do we truly need to provide support for this? Wouldn't it be simpler to just merge...

We store v1beta1 stuff as `jsonb` in postgres. And the field in the protobuff is also a `Any`. So we will be able to show v1beta1 even after we move...

I have created a TEP here https://github.com/tektoncd/community/pull/1055 to discuss in WG API call and bring attention to wider community.

Yes. I will target it after Event storage.

You will find these fields in a different location where they exist in v1beta1. We need to move to v1 from v1beta1. There's already an issue on that and TEP.

@avinal I assume you will work on v1beta1 to v1 conversion soon? These issues will keep coming up if we don't move to v1 soon.

@manuelwallrapp Yes, when we move to v1 in Results, it will be resolved.