dart-lang
Initial publish of `ok_http` and firehose setup
@natebosch Hi! @Anikate-De is close to finishing the implementation for ok_http so we will be looking to publish soon. Brian mentioned possibly (me) needing access to the labs publisher which I assume is related to this issue (I am unfamiliar with the publishing process for Dart packages). Is there anything I can do here?
Since this package hasn't been published, we might need to do the first publish manually. @devoncarew Have we ever used firehose to bootstrap a previously unpublished package? Should we try it and see if it works, or should I publish manually?
I think we can't set up the protected environment for example before the package exists. https://github.com/dart-lang/ecosystem/tree/main/pkgs/firehose#publishing-from-a-protected-github-environment
Maybe it's safe to set up the GitHub side and then configure pub after the first publish?
I'm not sure it's possible to bootstrap using firehose. I think you have to publish once (manually) then move the package into the target publisher, and use the package admin page to enable publishing-via-github.
I've only lightly used the publishing w/ an environment feature; I don't think it gets us the two-party review thing that we'd want, and adds another step to publishing. I'd recommend just avoiding it unless it adds more than I'm aware of.
Oh, I must have forgot that this already happened. https://github.com/dart-lang/http/blob/master/.github/workflows/publish.yaml
It looks like firehose doesn't support flutter packages though.
It looks like firehose doesn't support flutter packages though.
Oh interesting so after you do the first manual publish, we will have to continue to manually publish for every new version?
I think I'll just need to split the workflow up into two separate ones for the flutter and non-flutter packages. It looks like firehose has a config option for this.
Hmm
Message from server: Package name `ok_http` is too similar to another active package: `okhttp` (https://pub.dev/packages/okhttp).
@jonasfj - is there a workaround?
Pub deployment went through and I was able to publish. https://pub.dev/packages/ok_http/versions/0.1.0
Next step is to split the workflow file into flutter and non-flutter workflows