kcp CI Bot

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with `/remove-lifecycle stale`. If this issue is safe to...

@embik: Closing this issue. In response to [this](https://github.com/kcp-dev/kcp/issues/3121#issuecomment-2314426166): >Closing, since [v0.25.0](https://github.com/kcp-dev/kcp/releases/tag/v0.25.0) assets are looking fine and therefore there is a version with fixed checksums available. > >```sh >$ sha256sum -c...

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with `/remove-lifecycle stale`. If this issue is safe to...

Stale issues rot after 30d of inactivity. Mark the issue as fresh with `/remove-lifecycle rotten`. Rotten issues close after an additional 30d of inactivity. If this issue is safe to...

Rotten issues close after 30d of inactivity. Reopen the issue with `/reopen`. Mark the issue as fresh with `/remove-lifecycle rotten`. /close

@kcp-ci-bot: Closing this issue. In response to [this](https://github.com/kcp-dev/kcp/issues/2654#issuecomment-2195621115): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close...

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with `/remove-lifecycle stale`. If this issue is safe to...

Stale issues rot after 30d of inactivity. Mark the issue as fresh with `/remove-lifecycle rotten`. Rotten issues close after an additional 30d of inactivity. If this issue is safe to...

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with `/remove-lifecycle stale`. If this issue is safe to...

Stale issues rot after 30d of inactivity. Mark the issue as fresh with `/remove-lifecycle rotten`. Rotten issues close after an additional 30d of inactivity. If this issue is safe to...