Cirrus CI shut down on June 1, 2026 when Cirrus Labs joined OpenAI. cirrus-ci.org no longer resolves in DNS.
Cirrius support from #348 is still present in the codebase. Unfortunately this misleads AI coding agents. When I used an agent to research mapt's IBM Cloud support, it reported Cirrus persistent worker as a CI runner option alongside GH Actions.
The dead code also opens port 3010 in security groups, and this can mislead agents as well (a broken template for future code).
Can we remove pkg/integrations/cirrus/, related CLI flags, and security group settings for port 3010?
Cirrus CI shut down on June 1, 2026 when Cirrus Labs joined OpenAI. cirrus-ci.org no longer resolves in DNS.
Cirrius support from #348 is still present in the codebase. Unfortunately this misleads AI coding agents. When I used an agent to research mapt's IBM Cloud support, it reported Cirrus persistent worker as a CI runner option alongside GH Actions.
The dead code also opens port 3010 in security groups, and this can mislead agents as well (a broken template for future code).
Can we remove
pkg/integrations/cirrus/, related CLI flags, and security group settings for port 3010?