Skip to content

Revert downgrading bundler mismatches to a warning#2694

Merged
1 commit merged intomasterfrom
revert_warnings_downgrade
Mar 23, 2019
Merged

Revert downgrading bundler mismatches to a warning#2694
1 commit merged intomasterfrom
revert_warnings_downgrade

Conversation

@deivid-rodriguez
Copy link
Copy Markdown
Contributor

@deivid-rodriguez deivid-rodriguez commented Mar 23, 2019

This reverts commit dad8d25, reversing changes made to b4063c6.

Description:

#2621 broke bundler's build. I'm going to investigate why but in the meantime I don't want to have a red master in bundler so I'm reverting this.

I wonder if we should test rubygems against a vendored bundler that contains the code in bundler's master. Probably too much overhead 🤷‍♂️.

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.

This reverts commit dad8d25, reversing
changes made to b4063c6.
@deivid-rodriguez deivid-rodriguez changed the title Revert "Merge #2621" Revert downgrading bundler mismatches to a warning Mar 23, 2019
@hsbt
Copy link
Copy Markdown
Member

hsbt commented Mar 23, 2019

👌

We should unify the rubygems and bundler like rails/rails repository and use the master branches both.

@deivid-rodriguez
Copy link
Copy Markdown
Contributor Author

Yes. We definitely should...

@deivid-rodriguez
Copy link
Copy Markdown
Contributor Author

deivid-rodriguez commented Mar 23, 2019

Maybe we can add a single job to test this for now like in here 36e3736. A bit of overhead but not too much.

@deivid-rodriguez
Copy link
Copy Markdown
Contributor Author

@bundlerbot r+

ghost pushed a commit that referenced this pull request Mar 23, 2019
2694: Revert downgrading bundler mismatches to a warning r=deivid-rodriguez a=deivid-rodriguez

This reverts commit dad8d25, reversing changes made to b4063c6.

# Description:

#2621 broke bundler's build. I'm going to investigate why but in the meantime I don't want to have a red master in bundler so I'm reverting this.

I wonder if we should test rubygems against a vendored bundler that contains the code in bundler's master. Probably too much overhead 🤷‍♂️.

# 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).


Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
@ghost
Copy link
Copy Markdown

ghost commented Mar 23, 2019

Build succeeded

@ghost ghost merged commit 412fb8a into master Mar 23, 2019
@ghost ghost deleted the revert_warnings_downgrade branch March 23, 2019 13:35
This pull request was closed.
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