Replace bespoke Circle and GitHub build/smoke/image workflows with the canonical QQQ orb 0.7.9 All profile. Build once, smoke the resulting artifacts in core/full jobs, and retain develop-only image publication when the package is already public. The manual release workflow becomes a thin immutable caller using exact-source public Circle evidence without copying a token.
The hosted canary exposed an obsolete AWS SDK v1 MinIO adapter against current QQQ SDK v2 snapshots. Remove its client/action overrides and use the upstream endpoint/path-style metadata; preserve endpoint tests for every action and actual local HTTP listing/write assertions. No dependency pins or release preconditions are bypassed.
Validation: canonical callers, actionlint and 44 Python assertion tests pass. Local Maven compilation and unit tests pass (BOM 2; application 21 passing, two existing environment-dependent skips), including both MinIO tests. Four packaged tests passed; three packaged-listener cases failed on local WSL IPv6 unavailability. Those tests remain intact and hosted verification must pass. Release-shell behavior coverage moved to the orb in merged PR46.
No release was dispatched and no package bootstrapped. Actual hosted build/core/full smoke results, develop publication conditions, branch enforcement and release prerequisites remain to be verified before claiming completion.
Replace bespoke Circle and GitHub build/smoke/image workflows with the canonical QQQ orb 0.7.9 All profile. Build once, smoke the resulting artifacts in core/full jobs, and retain develop-only image publication when the package is already public. The manual release workflow becomes a thin immutable caller using exact-source public Circle evidence without copying a token.
The hosted canary exposed an obsolete AWS SDK v1 MinIO adapter against current QQQ SDK v2 snapshots. Remove its client/action overrides and use the upstream endpoint/path-style metadata; preserve endpoint tests for every action and actual local HTTP listing/write assertions. No dependency pins or release preconditions are bypassed.
Validation: canonical callers, actionlint and 44 Python assertion tests pass. Local Maven compilation and unit tests pass (BOM 2; application 21 passing, two existing environment-dependent skips), including both MinIO tests. Four packaged tests passed; three packaged-listener cases failed on local WSL IPv6 unavailability. Those tests remain intact and hosted verification must pass. Release-shell behavior coverage moved to the orb in merged PR46.
No release was dispatched and no package bootstrapped. Actual hosted build/core/full smoke results, develop publication conditions, branch enforcement and release prerequisites remain to be verified before claiming completion.
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.
Replace bespoke Circle and GitHub build/smoke/image workflows with the canonical QQQ orb 0.7.9 All profile. Build once, smoke the resulting artifacts in core/full jobs, and retain develop-only image publication when the package is already public. The manual release workflow becomes a thin immutable caller using exact-source public Circle evidence without copying a token.
The hosted canary exposed an obsolete AWS SDK v1 MinIO adapter against current QQQ SDK v2 snapshots. Remove its client/action overrides and use the upstream endpoint/path-style metadata; preserve endpoint tests for every action and actual local HTTP listing/write assertions. No dependency pins or release preconditions are bypassed.
Validation: canonical callers, actionlint and 44 Python assertion tests pass. Local Maven compilation and unit tests pass (BOM 2; application 21 passing, two existing environment-dependent skips), including both MinIO tests. Four packaged tests passed; three packaged-listener cases failed on local WSL IPv6 unavailability. Those tests remain intact and hosted verification must pass. Release-shell behavior coverage moved to the orb in merged PR46.
No release was dispatched and no package bootstrapped. Actual hosted build/core/full smoke results, develop publication conditions, branch enforcement and release prerequisites remain to be verified before claiming completion.