Bump dependencies; raise omnyhub to ^1.5.1 (1.56.1)#113
Merged
Conversation
A maintenance release: dependency constraints only. No API change, no behaviour change; the 813-test suite passes unmodified. omnyhub 1.4.0/1.5.0 are on-demand TLS releases and 1.5.1 is a dependency bump beneath them. Their changes are confined to the Let's Encrypt TLS provider, which OmnyShell does not use — the hub listener builds its TLS from ReloadableFileTls.directory or StaticTls.context, and nothing here touches LetsEncryptTls or DomainPolicy. 1.4.0's one breaking change, LetsEncryptTls.isAllowed now returning Future<bool>, has no caller here. omnydrive 1.12.3 is itself only a restatement of that constraint. The rest are routine: asn1lib, ffi, http, meta, path. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
lib/src/version.dart carries the version as a compile-time constant and test/unit/version_test.dart asserts it matches pubspec.yaml. The 1.56.1 bump left it at 1.56.0. 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.
A maintenance release: dependency constraints only. No API change, no behaviour change — the 813-test suite passes unmodified against these versions.
Changed
^1.5.1(from^1.3.0). 1.4.0 and 1.5.0 are on-demand TLS releases (asyncDomainPolicy,LetsEncryptTls.autoIssue,LetsEncryptTls.renewBefore) and 1.5.1 is a dependency bump beneath them. Their changes are confined to the Let's Encrypt TLS provider, which OmnyShell does not use: the hub listener builds its TLS fromReloadableFileTls.directoryorStaticTls.context, and nothing in the package touchesLetsEncryptTlsorDomainPolicy. 1.4.0's one breaking change —LetsEncryptTls.isAllowednow returningFuture<bool>— has no caller here. The surfaces OmnyShell is built on (OmnyHub,Service,TlsProvider, the node protocol) are unchanged.^1.12.3(from^1.12.2), itself only a restatement of the omnyhub constraint above.asn1lib: ^1.6.5,ffi: ^2.2.0,http: ^1.6.0,meta: ^1.19.0,path: ^1.9.1.Verification
Every CI gate was run locally before pushing:
dart analyze— no issuesdart test --platform vm— 813 passeddart format --set-exit-if-changed— clean (no.dartfiles touched)dart run dependency_validator— no issuesdart pub publish --dry-run— clean🤖 Generated with Claude Code