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

Improve rebar.config generation #1010

Merged
merged 1 commit into from
Nov 13, 2024
Merged

Improve rebar.config generation #1010

merged 1 commit into from
Nov 13, 2024

Conversation

essen
Copy link
Member

@essen essen commented Nov 13, 2024

We now provide the version as a tagged tuple indicating whether this is a branch, tag or ref. This should help rebar automatically upgrade dependencies, and remove an annoying warning when rebar is used.

In order to detect the type of version the dependencies must be available, therefore the rebar.config target now depends on the deps target.

To test this the Cowboy package version had to be changed from 1.0.4 to master. This is a breaking change, but I do not expect too many people to still use 1.0.4.

#900

We now provide the version as a tagged tuple indicating
whether this is a branch, tag or ref. This should help
rebar automatically upgrade dependencies, and remove
an annoying warning when rebar is used.

In order to detect the type of version the dependencies
must be available, therefore the rebar.config target now
depends on the deps target.

To test this the Cowboy package version had to be changed
from 1.0.4 to master. This is a breaking change, but I do
not expect too many people to still use 1.0.4.
@essen essen merged commit 5ee44b1 into master Nov 13, 2024
54 checks passed
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

Successfully merging this pull request may close these issues.

1 participant