Skip to content

Add a note for the non-semantically versioned case#2242

Merged
bundlerbot merged 1 commit intoruby:masterfrom
deivid-rodriguez:actionable_semver_warning
Mar 23, 2018
Merged

Add a note for the non-semantically versioned case#2242
bundlerbot merged 1 commit intoruby:masterfrom
deivid-rodriguez:actionable_semver_warning

Conversation

@deivid-rodriguez
Copy link
Copy Markdown
Contributor

Description:

Fixes #2228 by recommending another form of version specification when the overly strict dependency is not actually semantically versioned.


Tasks:

  • Describe the problem / feature
  • Write tests
  • Write code to solve the problem
  • Get code review from coworkers / friends

I will abide by the code of conduct.

@bronzdoc
Copy link
Copy Markdown
Contributor

Thanks! @bundlerbot r+

@bundlerbot
Copy link
Copy Markdown
Contributor

📌 Commit de025f8 has been approved by bronzdoc

@bundlerbot
Copy link
Copy Markdown
Contributor

⌛ Testing commit de025f8 with merge 44b724d...

bundlerbot added a commit that referenced this pull request Mar 23, 2018
…ronzdoc

Add a note for the non-semantically versioned case

# Description:

Fixes #2228 by recommending another form of version specification when the overly strict dependency is not actually semantically versioned.
______________

# Tasks:

- [x] Describe the problem / feature
- [ ] Write tests
- [x] Write code to solve the problem
- [ ] Get code review from coworkers / friends

I will abide by the [code of conduct](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md).
@bundlerbot
Copy link
Copy Markdown
Contributor

☀️ Test successful - status-travis
Approved by: bronzdoc
Pushing 44b724d to master...

@bundlerbot bundlerbot merged commit de025f8 into ruby:master Mar 23, 2018
@deivid-rodriguez deivid-rodriguez deleted the actionable_semver_warning branch March 23, 2018 02:17
bundlerbot added a commit that referenced this pull request Apr 24, 2018
Tweak warning recommendation

# Description:

In #2242 I introduced a recommendation to fix the semver warning in the case where the dependency is not semantically versioned. However, I think the recommendation was incorrect since, for example, `< 5.2` still allows `5.2.0.rc1`, whereas something like `~> 5.1.5` does not.

I was bitten by this when I updated my dependencies according to the recommendation and the `rails-5.2.0.rc1` gem installed on my system was unintentionally activated.

# Tasks:

- [x] Describe the problem / feature
- [x] Write tests
- [x] Write code to solve the problem
- [ ] Get code review from coworkers / friends

I will abide by the [code of conduct](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md).
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.

3 participants