Repository navigation
feat: render CCv2 build cleanup notifications - #17
Merged
Merged
Conversation
This was referenced Nov 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Render
ccv2.build-cleanup.completedthrough Notify's existing Slack and Teamsproviders, using the exact published
@commercekit-tools/notification-contract@0.0.4dependency. The presentationshows dry-run/apply mode, scope, retention, outcome, accepted deletion requests,
failures/unknowns, deferrals and duration. Deletion initiation is never described
as completed physical deletion. Webhook delivery and existing events are unchanged.
Published dependency and reproducible bundle
The original unpublished-contract blocker is resolved. Package 0.0.4 was
published by the authorized package-only workflow
from exact action-kit main
a03da9366e6483040d504a742c1a95413c1202cb, followingmerged version PR #11.
No release-tag/GitHub Release workflow was run.
Registry integrity:
sha512-y1kTB/s049V0DGLoQZd4s+vlFscShG5wS5g2H4WH6t6rRSOuJrKiCy42dcNlx5wC7NAy6hQuYoTFOQVQ1+PVoA==.This matches the tested publication tarball exactly (SHA256
02807ee404e55d3b523f855680f2fbb9e2630246604faed68a4d50bf8ab9a436).Notify pins 0.0.4 exactly in package.json and pnpm-lock.yaml. The reviewed
release-age exception is restricted to that exact package/version. Assertions
and current documentation match the installed package. The committed bundle
was rebuilt from a fresh normal registry installation, without local source
mounts, candidate aliases, fake registry versions or vendored schemas.
Final reviewed head:
c61064185a5c9e120d1c0ca48f921fe6f424bb1e.Bundle SHA256:
bc89d0c482b8b8cfa7fc024a2b21dcedfc28a5b86fc052fbd22708d437883f89.Validation
17 event fixtures, strict types, formatting/lint, unchanged old-event
golden snapshots, byte-identical bundle regeneration and public scan.
89.23% branches,97.50% functions,99.23% lines.
PASS on the exact reviewed head.
and CodeQL check
PASS on that same head.
No threshold, check, schema validation, audit or branch protection was bypassed.
The owner authorized merging when green. This is a source/bundle integration,
not an Action release, Git tag, deployment or live webhook delivery.
Companion integration and remaining operational gates
Production SAP eligibility remains unverified and real cleanup remains blocked;
package publication and this merge do not authorize deletion. The cleanup
producer's separate dependency upgrade from 0.0.3 to 0.0.4 is not part of this
Notify PR; its existing normal bundle continues to emit no cleanup event until
that producer upgrade is made. All consumer action pins should be immutable.