fix(db): extend to_version tidyr::nest [stale_floor]

[ndohpenngit]

What does this PR do?

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

Entry

tidyr::nest

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

Changelog evidence

The nest() API break and group-preservation behavior described remain valid through tidyr 1.3.2 (2025-12-19). Current CRAN is at 1.3.2; to_version 1.3.9 is beyond current release. Extend to 1.3.99 to cover the entire 1.3 series until next major version, capturing users still at 1.3.x who would be affected by the breaking changes introduced in 1.0.0.

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": "tidyr",
  "fn": "nest",
  "from_version": "0.8.99",
  "to_version": "1.3.99",
  "risk": "high",
  "description": "In tidyr 1.0.0, nest() and unnest() were overhauled with new syntax: nest(x, y, z) became nest(data = c(x, y, z)), and the first argument changed from data to .data. Additionally, nest() now preserves grouping from dplyr::group_by(), which affects downstream group-aware calls like mutate() and filter(). Old positional-column usage of nest() generates a translation warning but may not always translate correctly, and code relying on nest() *not* preserving groups may now silently behave differently.",
  "reference": "https://rdrr.io/cran/tidyr/f/NEWS.md",
  "added_by": "ndohpenngit",
  "added_date": "2026-06-11"
}