fix: change OpencertsRegistryVerifier status from INVALID to SKIPPED#127
fix: change OpencertsRegistryVerifier status from INVALID to SKIPPED#127
Conversation
📝 WalkthroughWalkthroughThis PR modifies the OpenCert registry verifier to emit Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
|
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/open-cert/verify.ts (1)
65-65:⚠️ Potential issue | 🟡 MinorStale comments still reference "invalid" status.
Line 65 and Line 197 both say
"if all issuers are invalid => invalid"but the status is nowSKIPPED. Update these comments to reflect the new semantics.Proposed fix
Line 65:
-// if one issuer is valid => fragment status is valid otherwise if all issuers are invalid => invalid +// if one issuer is valid => fragment status is valid otherwise if all issuers are invalid => skippedLine 197:
- // if one issuer is valid => fragment status is valid otherwise if all issuers are invalid => invalid + // if one issuer is valid => fragment status is valid otherwise if all issuers are invalid => skippedAlso applies to: 197-197
## [2.6.1](v2.6.0...v2.6.1) (2026-02-10) ### Bug Fixes * change OpencertsRegistryVerifier status from INVALID to SKIPPED ([#127](#127)) ([c1f49e1](c1f49e1))
|
🎉 This PR is included in version 2.6.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |



Summary by CodeRabbit
Release Notes