Antonio

Closing for now. Will make a proper ticket to track this.

Also please update the PR title to follow conventional commits (the CI fails due to that): https://www.conventionalcommits.org/en/v1.0.0/. This is probably a `docs:` PR.

Mhhh then I'd rather have the docs point to the release branch than to develop. I'm saying this because there'll soon be few PRs which make the docs outdated.

Correct.

@Ad96el @weichweich do you think we can merge this commit on the release branch and then cherry-pick it on `develop`? I am not sure if the changed README changes the...

@ChrisChinchilla can you check if anything needs to be updated, and then we can merge this?

Cool! I also saw how moonbeam does it, and tried to replicate it, but I was somehow having a duplicate definition error, since two different packages where trying to declare...

@rflechtner I pushed a commit to make sure we don't default to spiritnet when importing `@kiltprotocol/augment-api`. It's my personal opinion that we should be explicit about this. Anyway, I don't...

I'll review tomorrow, but I pulled in Tom as well for a review, since I would not rely on my own review for this stuff.

@arty-name just out of curiosity, how would a non-monorepo SDK look like? Still all packages in the same repo, I guess? And then each with its own `package.json` and without...