Update rabbit_common and amqp_client on hex.pm

[leonardb]

Community Support Policy

• I have read RabbitMQ's Community Support Policy

RabbitMQ version used

4.1.x

How is RabbitMQ deployed?

Other

Steps to reproduce the behavior in question

The latest release on hex.pm is 4.0.3

4.0.x is no longer supported and rabbit_common does not compile under OTP-28

4.1 contains fixes for at least having rabbit_common compile under OTP-28

Would it be please be possible to get updated packages for 4.1.x (4.1.3 is current) published to hex.pm?

[michaelklishin]

During the migration from Concourse to rabbitmq/server-packages, the job that publishes amqp_client did not make it.

It will take reintroducing a new job that would publish deps/rabbit_common, deps/amqp_client, and its AMQP 1.0 counterpart, I guess.

Right now both rabbit_common and amqp_client use erlang.mk for Hex.pm publishing. We can introduce a Rebar config file for each if that'd make a meaningful difference.

rabbitmq/server-packages is open source but because hex.pm account access is restricted to the core team, it's not really something that can be contributed.

I somewhat doubt that this can become a priority before RabbitMQ 4.2.0 ships this fall.