As part of runtime upgrade 1012 we changed how fees are configured.
We just opened a Council Motion to bootstrap the new fees storage for the CommitAnchor fee. The value remains the same as before, is just that we needed to populate the new storage with it.
All the best,