Pat

We could revert the PR and re-deploy the repos then with the old information but I'd rather come up with a solution that resolves it for both if possible. I'll...

Yeah, ultimately I'm not sure there is a good way to handle this - I was hoping there would be an option to notify of upcoming changes or similar. We...

https://github.com/fluent/fluent-bit/actions/runs/13673226103/job/38228444565 seems to be picking up the revert now - this is the staging release so I will promote once it is complete. ``` + APTLY_ORIGIN='. bullseye' + APTLY_LABEL='. bullseye'...

As always, the longest path is always the Windows builds :( Once complete I will promote to release and this should resolve the issue.

> [@patrick-stephens](https://github.com/patrick-stephens) Thank you for the swift resolution, it's saved me a lot of manual work. No worries, I would have done last night but it was EOD for me...

Current value (prior to releasing updated version) of `noble` release file: ```shell curl -sSfL https://packages.fluentbit.io/ubuntu/noble/dists/noble/Release Origin: packages.fluentbit.io Label: fluent-bit Suite: noble Codename: noble Date: Tue, 4 Mar 2025 09:17:23 UTC...

Release workflow running now: https://github.com/fluent/fluent-bit/actions/runs/13674323433/job/38231371508 ```shell + APTLY_ORIGIN='. jammy' + APTLY_LABEL='. jammy' ``` Note it takes a little while for the official server to sync the packages over.

Updated value of `noble` release file: ```shell $ curl -sSfL https://packages.fluentbit.io/ubuntu/noble/dists/noble/Release Origin: . noble Label: . noble Suite: noble Codename: noble Date: Wed, 5 Mar 2025 10:56:08 UTC Architectures: amd64...

@davidlawson83 / @vnovakovic-godaddy please can you confirm this is resolved now so we can close?

@jlecour we understand but what is the suggestion to prevent breaking existing users?