Repository navigation
chore: vendor verified production SDK 0.1.0-beta.188 - #95
Closed
mdbase-dev-release-automation[bot] wants to merge 1 commit into
Closed
mdbase-dev-release-automation[bot] wants to merge 1 commit into
mdbase-dev-release-automation[bot] wants to merge 1 commit into
Conversation
mdbase-dev-release-automation
Bot
force-pushed
the
automation/sdk-repin
branch
from
November 12, 2026 22:23
680eb0c to
97a4415
Compare
Contributor
|
Superseded by #96, which carries this repin commit unchanged plus the code move to the new SDK API. Main is on |
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.
SDK: @mdbase-dev/sdk@0.1.0-beta.188
Signed source: e8ffb806d16c58fe03cf50c96fb66e29ebb612ba (refs/tags/v0.1.0-beta.188)
Exact npm production SDK pin and byte-identical, provenance-verified intake archive and receipt. Existing LAB/staging originals, signatures, receipts and aliases remain unchanged. No deployment or store approval is granted.