Release to Production v2.9.16 - 2026-03-16#1854
Merged
transphorm merged 21 commits intomainfrom Mar 16, 2026
Merged
Conversation
* Align KMP verification result contract * formatting * pr feedback * feedback
* Handle missing parsed DSC before fetching * address cr feedback * formatting * fix bugs
…1834) * Align KMP verification result contract * formatting * pr feedback
* save sepc * save wip * save pr 2wip * save wip rd 3 * finalize ios crash fix * pr feedback and format
* update specs * update specs * pr feedback
* update specs * update specs * harden nfc apdu
* udates * add regression test * feedback; remove assets * fix pipeline * pr feedback * fixes * fix pipeline * finalize rn03 work * fix ci * better foramt
* update specs * update specs * harden nfc apdu * ns-05 work * pr feedback * updates * fixes
…implementations (SC-01) (#1841) * sc-01 first commmit * fix pipelines * fix build * add missing * pipeline fixes * last round of feedback
* sc-01 first commmit * fix pipelines * update specs * update specs to reflect paused work * fix build * add missing * pipeline fixes * last round of feedback * update specs
* push code for wv-02 and 03 * pr feddback
…1847) Versions 1.0.20 and 1.0.21 were published manually (not via CI), which bypassed the yarn pack step that resolves workspace:^ protocols. The published packages contain raw workspace:^ dependencies, making them uninstallable for external consumers. This version bump triggers a clean CI publish that correctly resolves @selfxyz/sdk-common to ^1.0.0.
* push code for wv-02 and 03 * save wip * fixes * pr feedback fix pipelines * save spec * address feedback * pr feedbacak * fixes * format * fix pipelines * fix * fix * fixes
Co-authored-by: Justin Hernandez <justin.hernandez@self.xyz>
* first commit sc-02 * prep for pr * fix * fix * check result
* first commit sc-02 * prep for pr * fix * specs pass 1 * update specs
Release to Staging v2.9.16 - 2026-03-13
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 19414827 | Triggered | Generic Password | 13f19dd | packages/mobile-sdk-alpha/ios/SelfSDK/PassportReaderCore.swift | View secret |
| 19414827 | Triggered | Generic Password | d7c1556 | app/ios/PassportReaderCore.swift | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
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
3 participants
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.
🎯 Production Release
Release Date: March 16, 2026
Commits ahead: 21
This automated PR promotes tested changes from
stagingtomainfor production deployment.What's Included
All changes that have been verified in the staging environment.
Note: This PR is directly from
staging, so new commits merged tostagingwill automatically appear here.Pre-Deployment Checklist
Deployment Notes
Merging this PR will trigger production deployment.
This PR was automatically created by the Release Calendar workflow on March 16, 2026