Version Packages - #348
Conversation
cf34d1a to
01bff01
Compare
PR SummaryLow Risk Overview The release notes document work already on Reviewed by Cursor Bugbot for commit 01bff01. Bugbot is set up for automated code reviews on this repo. Configure here. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #348 +/- ##
=======================================
Coverage 97.17% 97.17%
=======================================
Files 80 80
Lines 5410 5410
=======================================
Hits 5257 5257
Misses 153 153
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@sei-js/sei-global-wallet@2.0.1
Patch Changes
66deb15: Document that
@dynamic-labs/ethereum-aahas to match the@dynamic-labs/global-wallet-clientversion npm resolves, and keep the release checks on that resolved version instead of a constant.Dynamic declares
@dynamic-labs/ethereum-aaas an exact peer of its client and pins its internal packages to the client's version, so the two move together on every patch.@dynamic-labs/global-wallet-clientis a^4.96.3dependency here, which means a Dynamic patch inside that range changes the peer version consumers need. Pinning an older@dynamic-labs/ethereum-aathan the resolved client does not fail the install: npm cannot place the client's exact peer beside the older root copy, so it nests the client under this package and duplicates the whole Dynamic runtime. The Optional peer versions table now states this and shows how to read the version the resolved client asks for.The consumer verifier resolved
4.96.3regardless of what the range resolved to, so Dynamic publishing@dynamic-labs/global-wallet-client@4.96.4turned the nightly consumer run red on a duplicated Dynamic subtree rather than on any change in this repository. It now resolves the declared range against the registry, pins that client and the peer version it requests in each full consumer, and reports both, so a Dynamic patch is exercised the way an application receives it while a peer pin moving outside this package's published range still fails. A client that npm nests instead of hoisting is now reported as such, rather than as an unresolved dependency.No published dependency or peer range changes.