Don't increment Markdown version upgrade counter on first writes
What does this MR do and why?
The version upgrade counter is intended to measure only cache version upgrades (hence the name!), but right now it counts new rows as upgrades too:
This counter should've been at zero until the rollout began; right now we can't separate the rollout from the regular background of new writes, though you can tell if you look carefully.
References
- Documentation about how cache version bumps work: https://docs.gitlab.com/development/gitlab_flavored_markdown/banzai_pipeline_and_parsing/#phased-rollout-of-cache_commonmark_version-bumps
- Implementation of cache bumping mechanismhttps://gitlab.com/gitlab-org/gitlab/-/merge_requests/236200+
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.