Skip to content

fix(db): close entry tibble::tibble [stale_floor] - #91

Open
ndohpenngit wants to merge 1 commit into
mainfrom
fix/db-staleness-tibble-tibble
Open

fix(db): close entry tibble::tibble [stale_floor]#91
ndohpenngit wants to merge 1 commit into
mainfrom
fix/db-staleness-tibble-tibble

Conversation

@ndohpenngit

Copy link
Copy Markdown
Collaborator

What does this PR do?

Auto-generated by the staleness remediation agent.
Action: Close entry (window archaeologically unreachable)

Entry

tibble::tibble

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

Changelog evidence

The breaking change occurred in tibble 3.0.0 (2020-03-30), over 6 years ago. Current CRAN release is 3.3.1 (2025-06-08), 3+ major versions ahead of to_version 3.9.9. No realistic pharma/clinical user pinned to 2.1.99–3.0.x in 2026; the warning existed in 2.0.0 (2018), providing ~2 years notice. This window is archaeologically unreachable.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant