Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release request: 5.3 beta version #123

Open
libitx opened this issue Nov 5, 2019 · 3 comments
Open

Release request: 5.3 beta version #123

libitx opened this issue Nov 5, 2019 · 3 comments

Comments

@libitx
Copy link
Contributor

libitx commented Nov 5, 2019

I know the 5.3 branch is in development, but would it be possible to release a package in it's current state?

I am planning to release an Elixir library that depends on luerl, however mix requires all dependencies to be mix packages (as opposed to pointing to the github repo).

@rvirding
Copy link
Owner

rvirding commented Nov 19, 2019

How do you mean? In the master branch?

@libitx
Copy link
Contributor Author

libitx commented Nov 22, 2019

I can't publish a hex package that depends on a GitHub branch - it can only depend on published hex packages.

Therefore I have to publish the package depending on version 0.4, and then tell my users to override the dependency in their mix.exs to use your development branch:

eg:

def deps do
  [
    {:my_package, "~> 0.1.0"},
    {:luerl, github: "rvirding/luerl", branch: "develop", override: true}
  ]
end

It's all extra friction and it would just be helpful if my package could be published depending on luerl version 0.5.0-beta or whatever.

@rvirding
Copy link
Owner

@libitx Sorry I missed you last reply here. Would it be enough for me to create a tag 0.5.0-beta which points in to a branch, or does it have to be on the main branch?

Sorry for my github ignorance here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants