Turns out, this test was actually bad... The "answer" **should** be `1.0.1`, but our test was wrong. So I guess this indirectly fixes a really bizarre `berks update` bug that was never reported.