Repository navigation
Fix Storage identity in production release verification - #34
Closed
Craig Alvord (craxal) wants to merge 1 commit into
Closed
Craig Alvord (craxal) wants to merge 1 commit into
Craig Alvord (craxal) wants to merge 1 commit into
Conversation
Keep protected payload, receipt and immutable tag checks intact while matching the existing azure-storage package. Refresh affected catalog fixtures and current-release assertions. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2eadb772-b466-49f1-bcd0-2e2c59791222
Contributor
Author
|
Additional qualification: checked out exact Storage candidate 1a4bf6d in an isolated worktree and overlaid only this corrected verifier as a test fixture. node scripts/verify-plugin-marketplace.mjs --candidate passes every product, including Storage 0.3.1 with its immutable tag correctly pending. Production base a1f00ec separately passes, including released Storage 0.3.0 at azure-storage-v0-3-0-9347124. No payload, historical receipt or tag was changed. Focused verifier tests pass 20/20; both broader SRE documentation failures reproduce on untouched production main. Source compatibility and synchronized preferences acceptance are in coreai-microsoft/canvases-cloud-foundation#319; this PR remains verifier-only. |
This was referenced Oct 19, 2026
4 of 8 tasks
Alex Weininger (alexweininger)
approved these changes
Oct 23, 2026
4 of 8 tasks
5 of 9 tasks
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.
Summary
The production verifier rejects the existing Azure Storage package because its product map still uses
azure-storage-canvas. Match the reviewed catalog'sazure-storageidentity and paths so Storage candidates can be checked without bypassing package integrity.Changes
Release and governance checks
Evidence and handoff
Production base:
a1f00ec91e800233fe1b5d67c0814046aceac3fb. This is a separate correction for the existing verifier failure disclosed in #33, not a Storage package release.node scripts/verify-plugin-marketplace.mjs --candidatenow accepts every current production product, including Storage 0.3.0 at its existing immutable tag. Protected runtime, launcher, notices, icon and receipt tampering remain rejection cases.Focused
test/storage-release.test.mjsandtest/plugin-marketplace.test.mjs: 20/20 pass.The first complete production test run passed 43/45. The remaining
production catalog matches all installable plugins in orderandSRE package has its catalog identity, official preview logo and customer connection stepsfailures also reproduce on the untouched production base. Their unrelated SRE documentation expectations are not changed here.Storage source compatibility and preference-save synchronization fixes are being reviewed separately in the source repository. No generated bundle is edited by this PR.