Maximilian Fischer

Connecting to self hosted https servers already works. At least setting the host name instead of the organization worked for me. `zulip:///[email protected]/secret_api_key/[email protected]` But it does not seem to be documented.

@mtrezza @RodrigoSMarques If you want, I could have a look at this, too.

Some more information as I'm now home: Currently there is no recommended way to publish dart/Flutter packages to pub.dev automatically. The community uses the access and refresh token `pub publish`...

@mtrezza I'll have a look at it. Do you think it would be best to publish to pub.dev once a new github release has been created or should we consider...

@mtrezza I've created PR #719. It addresses the first point. Pub.dev does not support token authentication at the moment, as a result, the action requires the refresh and access token...

> 2\. if you are interested you can do that too based on how we already do it in the Parse JS SDK and I'll be on standby for any...

For now, they always had. But that's just how we did it. We could treat both as independent. (Dart package goes through the release cycle and the flutter one just...

Currently, they can just add `parse_server_sdk_flutter: ^3.1.0`. `parse_server_sdk: ^3.1.0` is then automatically added, since it is a dependency of `parse_server_sdk_flutter`. I we would release the packages independently (different versions) the...

[This](https://pub.dev/packages/melos) might be the tool we are searching for the auto-release workflow.

Just looked a little bit more into melos... It's definitely the tool for us. It even updates version/changelog based on git commits. I might go over some of the testing...