fix(db): extend to_version purrr::map2 [stale_floor]

[ndohpenngit]

What does this PR do?

Auto-generated by the staleness remediation agent.
Action: Extend to_version (stale ceiling)

Entry

purrr::map2

• Staleness: stale_floor
• Gap: from_version 0.3.99 << current 1.2.2 (>= 1 major version(s) behind)
• Reference: N/A

Changelog evidence

purrr 1.2.2 (2026-04-10) is current on CRAN, above the to_version 1.2.9 sentinel. The breaking change in recycling rules and name-recycling behavior introduced in 1.0.0 (2022-12-20) remains in effect through 1.2.2 with no reversion or adjustment. Users at versions 1.0.0–1.2.2 remain at risk if their code depends on the old pre-1.0.0 recycling semantics. Extend ceiling to 1.2.99 to cover the current release series and maintain accuracy.

Related issues

Part of the weekly staleness remediation run. Update the staleness tracking
issue once this PR is merged.

Type of change

• Bug fix
• New feature
• Database entry correction
• Documentation
• Other

Checklist

• Claim verified against official changelog (by agent)
• Human reviewer has spot-checked the changelog evidence
• validate CI check passes in reproducr-db
• sync_db.R runs cleanly after merge
• Tracking issue updated

Corrected entry

{
  "pkg": "purrr",
  "fn": "map2",
  "from_version": "0.3.99",
  "to_version": "1.2.99",
  "risk": "medium",
  "description": "In purrr 1.0.0, map2() adopted tidyverse recycling rules: only length-1 vectors are recycled; all others must have the same length. Code relying on implicit recycling of vectors whose length is a multiple of the other will now error. Additionally, map2() now recycles the names of its first input, which can produce differently-named output lists compared to purrr < 1.0.0.",
  "reference": "https://purrr.tidyverse.org/news/index.html#purrr-100",
  "added_by": "ndohpenngit",
  "added_date": "2026-06-17"
}