Adopt the centrally managed 0.8 orb patch track, now including the verified 0.8.1 browser-repository fix. Compatible patch fixes will apply without another per-repository version PR.
The shared rollout tool preserves the existing manifest profile and publication policy. Only .circleci/config.yml and .qqq-ci.yml change. Feature and default-branch configurations were rendered from this signed commit; QBit maintenance commits retain verification without publishing application artifacts. Native shared-worker pins and existing security settings are unchanged.
This pin upgrade does not certify outstanding scanner ownership, enforcement or release-path gaps; those remain tracked separately. Normal required checks must pass before merge.
Adopt the centrally managed 0.8 orb patch track, now including the verified 0.8.1 browser-repository fix. Compatible patch fixes will apply without another per-repository version PR.
The shared rollout tool preserves the existing manifest profile and publication policy. Only .circleci/config.yml and .qqq-ci.yml change. Feature and default-branch configurations were rendered from this signed commit; QBit maintenance commits retain verification without publishing application artifacts. Native shared-worker pins and existing security settings are unchanged.
This pin upgrade does not certify outstanding scanner ownership, enforcement or release-path gaps; those remain tracked separately. Normal required checks must pass before merge.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adopt the centrally managed 0.8 orb patch track, now including the verified 0.8.1 browser-repository fix. Compatible patch fixes will apply without another per-repository version PR.
The shared rollout tool preserves the existing manifest profile and publication policy. Only .circleci/config.yml and .qqq-ci.yml change. Feature and default-branch configurations were rendered from this signed commit; QBit maintenance commits retain verification without publishing application artifacts. Native shared-worker pins and existing security settings are unchanged.
This pin upgrade does not certify outstanding scanner ownership, enforcement or release-path gaps; those remain tracked separately. Normal required checks must pass before merge.