Conversation
This plugin is used to publish to hex.pm. This boils down to two steps: * `rebar3 hex user auth` (authenticate with hex.pm) * `rebar3 hex publish` (publish to public hex.pm)
|
Thanks @evnu -- I will merge this. Regarding the warning on Regarding notifying the people responsible to hex.pm, I think they get these PR notifications, but I will cc: them anyway (hi @ferd!). However, note that PropEr version 1.4.0 is not ready to be published yet. It will be once you see me changing the badge / README on GitHub. |
|
You actually don't want this plugin, now everyone using PropEr gets to download the hex plugin that way. It should instead go in Generally we advise that only project owners use the hex plugin to publish, and that can be done using a global plugin rather than the local one. In any case, we publish the rebar3_hex package with mix so that it is better supported for Elixir folks without having to specify the I can publish new versions of PropEr to hex without a problem (once it is ready), but I would revert this commit first, since it will likely "pollute" builds and not add anything required for users of the library. |
|
@ferd Thanks for clarifying this! |
|
I've created a PR (#214) that reverts this -- also, see a comment there. |
This pull request is a follow-up to #211 and alfert/propcheck#121. The pull request adds the rebar3_hex plugin to allow publishing to hex.pm. If the user is already registered with hex.pm, publishing boils down to two steps:
rebar3 hex user auth(authenticate with hex.pm)rebar3 hex publish(publish to public hex.pm)Note that compiling with
rebarfrom the repository itself results in a warning, but the build completes:@kostis Can you CC the people responsible for publishing to hex.pm? I tried the plugin using a small example project, but did not dare to try
rebar3 hex publishwithin PropEr itself.