Search…
⌃K

Publishing Packages

Permissions

Only Uploaders may publish a package. Each edition of OnePub defines an Uploader differently.
Free/Pro
Team
Enterprise
As all Members are Uploaders any Member can create a new package by running 'dart | flutter pub publish'.
All packages are associated with the Default Team and as such all Members have access to the package.
As all Members are Uploaders any Member can create a new package by running 'dart | flutter pub publish'.
To share a package it must be associated with a Team which only Team Leaders and/or Administrators may do.
As all Members are Uploaders any Member can create a new package by running 'dart | flutter pub publish'.
To share a package it must be associated with a Team which only Team Leaders and/or Administrators may do.
The secret to successfully publishing a package is.... good documentation.
Add a readme.md, take some time to document your public API and throw in some examples.

Publishing

If this is your first time publishing a package then you might find our blog article on publishing useful:

Mark package as private

To prepare a package for uploading to OnePub you must mark it as a private package.
Run the onepub pub private command:
onepub login # if you are not already authed
onepub pub private
This has the effect of adding a publish_to key to your pubspec.yaml file.
And now publish your package:
dart pub publish
Note: you can add the publish_to key manually by following the hard way instructions.

Public Packages

Some members may need to publish both private and public packages.
All public packages should be published directly to pub.dev using the standard dart tooling/processes.
Public packages you upload to pub.dev will be cached on onepub.dev within a few minutes of you publishing to pub.dev, so you can easily find these packages all on OnePub.