Tag breaking release

[serenity4]

#140 introduced a breaking change to the method_info data structure, requiring a breaking release.

We had thought of deferring this breaking release until a new change to Revise that may require breaking changes. See timholy/Revise.jl#904 (comment) for context on the opening of this PR.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.60%. Comparing base (c0ca2ff) to head (eec94b7).
Report is 4 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #142   +/-   ##
=======================================
  Coverage   69.60%   69.60%           
=======================================
  Files           3        3           
  Lines         408      408           
=======================================
  Hits          284      284           
  Misses        124      124           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[timholy]

I should have some time by mid-week next week. I'd like to get the include(mappingfunc, filename) change in too, but then let's make the release.

[serenity4]

Here are my changes (still very WIP) for mapexpr, FYI: serenity4/Revise.jl@master...mapexpr

I also don't mind waiting until I find some time to finish it, if you have a strong preference toward having both in before issuing a breaking release.

[timholy]

I've verified that we can add include(mapexpr, file) support in a non-breaking way. However, we first need to decide whether we want #141, which would be breaking. So sadly we need to hold this just a tiny bit longer. Sorry for the unconscionable delay!