-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
formula: deprecate!/disable!: deprecate missing or non-ISO 8601 dates. #9478
formula: deprecate!/disable!: deprecate missing or non-ISO 8601 dates. #9478
Conversation
Review period will end on 2020-12-10 at 11:03:42 UTC. |
There might be some value in adding a style check until 2.7.0. Not sure how often we disable/deprecate formulae but given that we just released 2.6.0 it feels like this will be sitting here for a while |
Sorry, fat fingers 🤦 |
2.7.0 will probably be a bit quicker than the wait from 2.6.0 because we've got a few pending deprecations queued up. |
Okay. It's probably not a huge deal, anyway. We can always batch-add dates to deprecate! and disable! when the time comes if needed, so that's fine. |
@fxcoudert has already done that in Homebrew/homebrew-core#66549 🎉 |
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.
LGTM. Tested locally and appears to work as expected.
CI failures will be resolved elsewhere
@MikeMcQuaid sorry I think you'll need to force push again, I found one formula I had missed: Homebrew/homebrew-core#66564 |
Rerunning the job should be enough because CI pulls in the latest master branch from homebrew-core. May as well wait until it's merged into linuxbrew-core as well. Plus, if this is waiting for 2.7.0, it should probably be rebased again then anyway |
Review period ended. |
As requested in Homebrew/homebrew-core#66360.
Do not merge until we're ready to tag 2.7.0.