consolidated sdk-versions
Yo @dayhaysoos-tbd congrats on getting that PR in! Loving this single
sdk-versions.json
How do you feel about this?
1) @leordev are these modules aligned with the ones you're coordinating for release with the SDK DRIs in your table of the Release Checklist?
2) @dayhaysoos-tbd Under "Maven", I think web5 should be one thing. All submodules of web5-kt are on the same release cycle. Is there a reason you have on the docs side to list these separately? And web5-crypto is on a different version from the others; typo?
3) In testsuite-kotlin we actually don't even explicitly declare a dependency on web5-kt at all; it's brought in transitively via tbdex-kt.
4) Should we change maven to jvm? Looks to me like your categories are about the runtime (ie. "js", not the build system we're using).
5) @leordev - Nick's versions definitions atop split out tbDEX JS submodules as different things like we do for Web5. ie. @tbdex/protocol. Should your Release Checklist do the same? I think right now it's in there as one entry tbdex-js.4 Replies
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
Yah totally - this was the first I could have a look 🙂
Iterate sounds great
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
Yeah great to raise - so yes this is clearly a case where we need separation even while the test cases may make a top level dependency declaration and bring everything else transitively