Web5

W

Web5

TBD54566975 – developer.tbd.website

Join

example reference

Hey @codermickey can you remind @finn-tbd and me the example reference you liked that made everything discoverable? Was it Vite?

Approach to Dev Site Refresh 🧵

Approach to Dev Site Refresh 🧵

Triage Dev Site Issues

🧵 for triage of all open developer.tbd.website issues so we have a clear tracker. This work will start Monday, DRI is @dayhaysoos-tbd

docker-compose Failure

So I'm seeing transient failures, for instance here: ``` Run docker-compose up -d dwn-server /home/runner/work/_temp/2d83f0ca-d1b7-4caf-ac8c-c0168939c60a.sh: line 1: docker-compose: command not found...

Merging Test Failures to `main` (Fixed)

Merging Test Failures to main (Fixed) 🧵

consolidated sdk-versions

Yo @dayhaysoos-tbd congrats on getting that PR in! Loving this single sdk-versions.json How do you feel about this? ```...

Kotlin dependency updates on testsuite.

@AceKYD They're all brought in transitively via here

@finn-tbd @codermickey Been looking at [

@finn-tbd @leordev Been looking at JReleaser - curious what this can do to help us unify release actions across the suite and simplify it in the process. WDYT?

SDK Upgrades

Hey @devRel - @leordev and @finn-tbd and I looking at making upgrades into latest Web5/tbDEX easier for y'all to stay on top of. Will write more about that later in a new thread. For now we came across a couple questions 1) When we're instructing folks to install Web5/tbDEX, are we always noting the version the docs are targeting? ie. explicitly telling the user to install a version, not "latest" or "default"? 2) Where are all the places we do this? For instance Quickstart has it here and we'd do a PR to make the version more explicit in the npm install command...

NoClassDefFoundError on PfiStructureTest

NoClassDefFoundError on PfiStructureTest PR 🧵

Trial of upgrading to Docusaurus v3🧵

Trial of upgrading to Docusaurus v3🧵

❌ Security and License Checks

❌ Security and License Checks

Fixing Version Issues HOWTO 🧵

Fixing Version Issues HOWTO 🧵

Kotlin PFI PR

Make it happen, Cap'n.

`tbdex` Available in TestSuite 🧵

tbdex Available in TestSuite 🧵

**Blocker ** Adding `tbdex-kt` Support

Blocker Adding tbdex-kt Support

New languages tests

@leordev @dayhaysoos-tbd Before I forget, we should have a look at making pipelines for the developer.tbd.website build. Adding language support for N languages means each has a new runtime and backing repo, and if those are serial in the build, our PR times are gonna take forever to run. So if we put them in pipelines and make the test runs parallel, we can cut out a lot of that cruft. Early thoughts?...

Kotlin Test Support

Starting a thread for coordinating Kotlin testsuite and code snippit work 🤘🏻
Next