docs(changelog): release v0.4.2#86
Conversation
GHCR sorts package versions by most-recent push timestamp. When actions/attest@v4 pushes the attestation referrer manifest after the image push, it becomes the most-recent artifact and displaces real tags (latest, x.y.z, x.y) in the UI, showing only the sha256 digest link instead. Remediation: loop over all tags from steps.meta.outputs.tags (using docker buildx imagetools create) after attestation completes. This re-touches each real tag, bumping their timestamp above the attestation referrer, so GHCR UI surfaces them first. Refs: #74
fix(ci): promote all image tags after attestation for GHCR UI
…ixes Following @it-consultant retrocontrol on PR #75 (issue #74), introduce a new workflow step requiring PR bodies to declare root assumption, pre-merge validation, post-merge validation plan, and rollback contingency for any CI or release-workflow change that depends on undocumented third-party service behavior (GHCR sort key, registry tag indexing, etc.). Steps 14-20 renumbered to 15-21. Internal Step reference in RELEASE VERIFICATION updated. Step 20 RETRO now audits step 14 clauses. Refs: #74, #75
chore(claude-md): add step 14 hypothesis check for CI/external-deps fixes
fix(docker): bump tzdata Alpine pin from 2026a-r0 to 2026b-r0
Bumps [github.com/aws/aws-sdk-go-v2/service/s3](https://github.com/aws/aws-sdk-go-v2) from 1.99.1 to 1.101.0. - [Release notes](https://github.com/aws/aws-sdk-go-v2/releases) - [Commits](aws/aws-sdk-go-v2@service/s3/v1.99.1...service/s3/v1.101.0) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go-v2/service/s3 dependency-version: 1.100.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…github.com/aws/aws-sdk-go-v2/service/s3-1.100.1 deps(deps): bump github.com/aws/aws-sdk-go-v2/service/s3 from 1.99.1 to 1.101.0
Bumps [github.com/aws/aws-sdk-go-v2/config](https://github.com/aws/aws-sdk-go-v2) from 1.32.16 to 1.32.17. - [Release notes](https://github.com/aws/aws-sdk-go-v2/releases) - [Commits](aws/aws-sdk-go-v2@config/v1.32.16...config/v1.32.17) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go-v2/config dependency-version: 1.32.17 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…github.com/aws/aws-sdk-go-v2/config-1.32.17 deps(deps): bump github.com/aws/aws-sdk-go-v2/config from 1.32.16 to 1.32.17
Bumps [github.com/klauspost/compress](https://github.com/klauspost/compress) from 1.18.5 to 1.18.6. - [Release notes](https://github.com/klauspost/compress/releases) - [Commits](klauspost/compress@v1.18.5...v1.18.6) --- updated-dependencies: - dependency-name: github.com/klauspost/compress dependency-version: 1.18.6 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…github.com/klauspost/compress-1.18.6 deps(deps): bump github.com/klauspost/compress from 1.18.5 to 1.18.6
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Type of change
Testing
Related