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
Hello! 👋 Is it possible to create release tag 1.3.0 or 1.2.1 please? I am referencing this package in my project as follows:
defp deps do
{:paginator, "~> 1.2.0"}
end
but there are several commits including this PR that are not tagged yet.
I did change my deps definition to: {:paginator, git: "git@github.com:duffelhq/paginator.git", branch: "main"} but I think it would be better to just create a new tag because I would not want major updates to break my code 🙏
The text was updated successfully, but these errors were encountered:
which will avoid the issue of updates to main breaking your code.
The downside to both these approaches is that using git instead of hex to pull in a dep doesn't populate the dep's dependencies in the mix.lock, so ... bump! :D
Hello! 👋 Is it possible to create release tag
1.3.0
or1.2.1
please? I am referencing this package in my project as follows:but there are several commits including this PR that are not tagged yet.
I did change my deps definition to:
{:paginator, git: "git@github.com:duffelhq/paginator.git", branch: "main"}
but I think it would be better to just create a new tag because I would not want major updates to break my code 🙏The text was updated successfully, but these errors were encountered: