Hello, I'm tim, I'm the pm for the package stage, and today I was hoping to highlight a few issues that we have scheduled for milestone 14.4.

So, if you're interested, I recommend you check out these planning issues. They contain a lot of helpful information about what what we're working on. Why and how we can, how we iterate and break down issues for the container registry. I think it would be helpful to highlight in case you aren't aware we have a pretty significant update that we're planning to the container registry for early next year.

It will launch online garbage collection, but also unblock a bunch of other features that we have scheduled more to come on that, but for for this milestone, we're primarily focused on testing and writing production readiness review so that when we deploy the code to production, we know it works for the dependency proxy. We have a few issues scheduled uh this one worth mentioning is adding a time to life policy for the feature so right now you could use the dependency proxy to proxy and cache images from docker hub.

This will those those blobs and manifests are added to object storage. This will just basically say clear: the cache after 90 days by default. um You can also configure this yourself using the api and in subsequent milestones, we'll add a this disinformation to the user interface, which is what this next issue is all about. So we've been adding a graphql api for the dependency proxy. We want to convert the user interface to use view so that we can use this graphql and totally update and redesign the dependency proxy ui.

So we expect that work to start in 14.5, but this is laying the groundwork for it and then finally we're doing something similar for the package details page we're converting it to use to actually start to consume the graphql endpoints that we've created. So it's going to make the page more performant, reduce I'm sorry more performant and also give us more flexibility to add features in the future.

So this milestone very exciting a lot of testing a lot of getting ready and a lot of prepping for features that are going to really revamp the package stage in the coming milestones.

Thank you so much if you'd like to learn more, please feel free to reach out in an issue, and I look forward to talking to you there thanks.