You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may not be a bug but it seems a little unusual to me. It seems all non PR builds are been published to Maven. I noticed this because I have a giter8 project which attempts to use the latest stable version of munit-cats-effect-2 and the search used by giter8 only returns non release builds. This is different behaviour to how munit publishes builds as can be seen from the search result.
The text was updated successfully, but these errors were encountered:
Ah, thanks for the explanation @rossabaker 🙂 I guess I'll leave the issue open for now and let the maintainer(s) decide if it's desired behaviour or not.
Just highlighting that this issue still exists. The search used by giter8 returns non release builds. Maybe this is considered a giter8 issue rather than an issue with the way builds are been published by this library? 🤔
This may not be a bug but it seems a little unusual to me. It seems all non PR builds are been published to Maven. I noticed this because I have a giter8 project which attempts to use the latest stable version of
munit-cats-effect-2
and the search used by giter8 only returns non release builds. This is different behaviour to how munit publishes builds as can be seen from the search result.The text was updated successfully, but these errors were encountered: