Hi everyone 
The latest Sampo releases improved Hex/Elixir support (we now recognise @version module attributes in mix.exs), clearer CLI exit codes to distinguish success with no pending changes, and a bunch of bug fixes.
Also, thanks to Rafael Audibert from PostHog (who are in the process of adopting Sampo to publish their various SDKs), we’ve added support for PHP (Packagist) and Python (PyPI).
If you give it a try, I’d really appreciate any feedback or edge cases you run into 
and one more manual step you forgot is to update your README.md with the newly released version
Hi @a-maze-d ,
Just to clarify that all stages of @dimitarvp 's message are covered by Sampo. But not « update your README.md with the newly released version » , because I don’t think many projects have the version hard-coded into their README? Most project generally use shields?
But if you have a use case that I haven’t thought of, don’t hesitate to clarify, and I can possibly add the feature to Sampo.
To clarify, I mostly meant update the Elixir code block that advises which version to put inside your mix.exs. 
@GoulvenClech, sorry for the delay to answer.
Use cases I see missing are those where you have markdown/text files, like the README.md where you give instructions how to install your library. The default mix new my_app will create such instruction and therefore it’s common to see it in Elixir libraries (and I do like it because you can easily copy&paste it)
There are other use cases like livebook examples, or installation instructions in docs.
As the last example illustrates, it can even be within a link
For docs you can maybe get away with using a handcrafted mix job that you can run before the docs are created, but it would be neater if Sampo would support it
I hope that makes sense