set baseBranch=development in .changeset/config.json

[OmarTawfik]

cc @kanej

[kanej]

Our current publishing instructions are not leveraging changeset (our current changelog is based on Keep a changelog format, which isn't supported).

The publish instructions under ./docs/publish-extension.md suggest opening a release branch against main when putting together the release commit. It is at that point, I typically compare any changesets that have been added and update the changelog manually - hence the baseBranch of main.

My intent was to switch to a full changeset setup with automatic release from github ci on PR merge into main. But that remains an intention currently.

I am happy to see the changeset base branch changed to development if you are more comfortable putting together the release commit on development.

[OmarTawfik]

I looked at the instructions you sent, and it appears that CD involves multiple steps with secrets/env setup. I was just trying to unblock running changeset locally, but it seems there are a few other things that need to be done as well. I would rather not update/change anything right now, and risk breaking the pipeline, so I will leave it for now.