Bump versions to latest #336
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. we either pin to a specific version or not (we chose to pin) 2. we shouldn't use ~> in pre-1.0 versions, because there's no guarantees whatsoever in SemVer; 0.3.1 might break interface, and that's acceptable
i.e. GitHub changes -latest under the hood and there goes your CI :)
This reverts commit 53767cc.
We have a lot of unknown types, from rebar3 and want to avoid having to deal with that
We'd removed the ~> but forgot to bump the version
We inherit this from the "parent" config.
paulo-ferraz-oliveira
force-pushed
the
chore/bump-versions-to-latest
branch
from
8a3aba4
to
1182ae4
Compare
starbelly
approved these changes
Jun 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This also:
latestto a specific version (Ubuntu runner)unknownto Dialyzer's analysis config.