Set 2026-10-17 as release-candidate day, and install from CRAN first - #83
Merged
Merged
Conversation
The maintainer set 2026-10-17 as the joint 1.0 release-candidate day. ROADMAP.md's v1.0.0 section records the timeline: - the release-candidate scheme both packages share: DESCRIPTION 0.99.0, tag v1.0.0-rc.N, tag only, fixtures named handoff-<fit>-v0.99.0.rds; - what happens on the day: agreement_summary() removed, version 0.99.0, v1.0.0-rc.1 tagged, then the fixture round and the drafts; - the CRAN submission after it, no sooner than about a month after the later of the two acceptances, per CRAN's update-interval policy, and only on the maintainer's go-ahead. The CRAN criterion now records contentvalidR 0.4.0's acceptance on 2026-09-28 (#14, closed), and the fixture criterion covers nomologR's tests against producers 0.6.0 through 0.9.0. contentvalidR is on CRAN, so the README gives install.packages() first, carries a CRAN badge, and explains why CRAN's version can trail the newest release on R-universe. NEWS says the same. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JUhalt
added a commit
that referenced
this pull request
Sep 28, 2026
Release contentvalidR 0.10.0 Stamps the version, release notes, citation metadata, README, and roadmap for the tenth public release, the last planned before the joint 1.0 release candidate on 2026-10-17. It adds figures for papers, posters, and teaching: content_evidence() with its item flow diagram and item evidence profile, the rating-distribution view, and the apa switch (#82). It also states the handoff contract nomologR reads (#79), makes this package's walkthrough the joint one (#80, #81), separates the Delphi printout's caveats from its teaching (#78), and records the release-candidate timeline (#83). No computed value changes: 25 analyses across every workflow return the same values as v0.9.0. No breaking changes: the plot methods gain arguments after their existing ones. agreement_summary() remains deprecated and is removed in 1.0.0. contentvalidR 0.4.0 has been on CRAN since 2026-09-28. CRAN asks for updates no more often than every one to two months, so 0.10.0 is released on GitHub and R-universe only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs only: no code, no computed value, and no handoff change.
Release-candidate day: 2026-10-17
The maintainer set Saturday 2026-10-17 as the joint 1.0 release-candidate day. The v1.0.0 section of
ROADMAP.mdnow records the timeline:DESCRIPTIONsays 0.99.0, and the candidate is the git tagv1.0.0-rc.N. It is a tag only, never a GitHub release, because R-universe publishes GitHub releases to users. Candidate fixtures are namedhandoff-<fit>-v0.99.0.rds.agreement_summary(), set the version to 0.99.0, tagv1.0.0-rc.1, deliver the fixture set to nomologR, then draft the compatibility table, the shared handoff example, and the release notes.It also updates two criteria:
nomologR has been told the date.
Installing from CRAN
contentvalidR is on CRAN, so the README now:
install.packages("contentvalidR")first;NEWS gets an "On CRAN" section.
Verification
tools/release-gate.Ron this PR's head (abf19c8), run in a detached worktree: build, smoke, and check all pass. R CMD check: 0 errors, 0 warnings, and only the two expected notes (CRAN incoming feasibility, "Days since last update"; math rendering skipped without V8).🤖 Generated with Claude Code