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
Check deprecated methods on release #2673
Conversation
This is what one currently gets by running
I guess we should delay the removal of these to rubygems 4.0 (2019/12, I guess). |
be23d02
to
4712d2b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh this is great! thanks @deivid-rodriguez!
util/cops/deprecations.rb
Outdated
# deprecate :safdfa, nil, 2019, 02 | ||
# | ||
# # good | ||
# deprecate :safdfa, nil, 2019, 03 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just noticed that this example doesn't match the code. If we try to release a major version, and rubocop finds a method that's supposed to be removed in that same month, it will print an offense, although it's documented as "good" here. I'll fix it now.
Make sure we remove expired deprecations upon release.
4712d2b
to
fe67f62
Compare
I corrected the tiny documentation change, this should be ready now! |
@bundlerbot r+ |
2673: Check deprecated methods on release r=bronzdoc a=deivid-rodriguez # Description: I noticed that we have a bunch of methods in the code base that were supposed to have been deprecated in December 2018, when rubygems 3 was released, but that didn't happen? I'm not sure if it was intentional or not, but I figured we could have a release check that makes sure we either definitively remove the methods, or expand the deprecation horizon. # 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). 2676: Fix metadata description docs r=bronzdoc a=sonalkr132 # Description: > settable by gem authors without requiring an update to the rubygems software. this has never been true. Not sure why it said that. Using G in the gem is converting it to link on using `rake spec_guide` ([broken here](rubygems/guides@2ca58b0#diff-a0ed24268b853e4412f766326125de00L12)). # 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](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md). Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net> Co-authored-by: Aditya Prakash <aditya.prakash132@gmail.com>
Build succeeded |
2704: Remove long ago deprecated methods r=bronzdoc a=deivid-rodriguez # Description: Use our `deprecate` helper so that we don't forget to kill this code in the next major release (thanks to #2673). The diff is simple, view it without whitespace changes though. Or maybe I should just go ahead and kill all this code now... 🤔. # 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>
2673: Check deprecated methods on release r=bronzdoc a=deivid-rodriguez # Description: I noticed that we have a bunch of methods in the code base that were supposed to have been deprecated in December 2018, when rubygems 3 was released, but that didn't happen? I'm not sure if it was intentional or not, but I figured we could have a release check that makes sure we either definitively remove the methods, or expand the deprecation horizon. # 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). 2676: Fix metadata description docs r=bronzdoc a=sonalkr132 # Description: > settable by gem authors without requiring an update to the rubygems software. this has never been true. Not sure why it said that. Using G in the gem is converting it to link on using `rake spec_guide` ([broken here](rubygems/guides@2ca58b0#diff-a0ed24268b853e4412f766326125de00L12)). # 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](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md). Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net> Co-authored-by: Aditya Prakash <aditya.prakash132@gmail.com>
Description:
I noticed that we have a bunch of methods in the code base that were supposed to have been deprecated in December 2018, when rubygems 3 was released, but that didn't happen?
I'm not sure if it was intentional or not, but I figured we could have a release check that makes sure we either definitively remove the methods, or expand the deprecation horizon.
Tasks:
I will abide by the code of conduct.