Upgrade to omnyhub 1.5.1 (1.12.3) - #20
Merged
Merged
Conversation
Raise the omnyhub constraint to ^1.5.1. omnyhub 1.4.0 and 1.5.0 are on-demand TLS releases (async DomainPolicy, LetsEncryptTls.autoIssue, LetsEncryptTls.renewBefore), and 1.5.1 is a dependency bump beneath them. Their changes are confined to the TLS provider, which omnydrive does not use: both servers build their transport with HttpTransport.http, and nothing in the package touches LetsEncryptTls, DomainPolicy or TlsProvider. 1.4.0's one breaking change, isAllowed now returning Future<bool>, has no caller here. The HTTP surface omnydrive is built on is unchanged. Verified by resolving and running the full suite against 1.5.1: format clean, analyzer clean, dependency_validator clean, all 260 tests pass. No behaviour or API change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
1 participant
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.
Changed
^1.5.1(from^1.3.0).A maintenance bump only. omnyhub 1.4.0 and 1.5.0 are on-demand TLS releases (async
DomainPolicy,LetsEncryptTls.autoIssue,LetsEncryptTls.renewBefore), and 1.5.1 is a dependency bump beneath them. Their changes are confined to the TLS provider, which omnydrive does not use — both servers build their transport withHttpTransport.http, and nothing in the package referencesLetsEncryptTls,DomainPolicyorTlsProvider.1.4.0's one breaking change —
LetsEncryptTls.isAllowednow returningFuture<bool>— has no caller here.The omnyhub surface omnydrive is built on —
OmnyHub,HttpTransport,HubRequest/HubResponse,RouterService,successEnvelope/errorEnvelope,mapErrors— is unchanged. No behaviour change, no API change.Verification
Resolved and ran the full suite against omnyhub 1.5.1:
dart format— cleandart analyze --fatal-infos --fatal-warnings— no issuesdart run dependency_validator— no issuesdart test— 260/260 passdart pub publish --dry-run— clean🤖 Generated with Claude Code