I think you forgot to bump the version for the new release, at least
`mepo -v` still outputs 1.1 as version.

On Mon, Nov 28, 2022, at 12:45 PM, laalsaas wrote:
> I think you forgot to bump the version for the new release, at least
> `mepo -v` still outputs 1.1 as version.

Thanks for mentioning, since there were no end-user API / mepolang
updates for 1.1.1 from 1.1, I consider this a bug for 1.1 but I don't
plan to publish 1.1.2 revision just for this. Its noted that I'll make
sure to bump the version number for minor revisions for future releases.