Repository navigation
Prepare v0.5.0 release - #53
Merged
Merged
Conversation
…comments Bump Version to 0.5.0. Promote the NEWS development section to a 0.5.0 heading and restructure it the way 0.4.0 was: breaking changes first (the #38 seed-contract change, now with an explicit migrating paragraph telling users to regenerate pinned expected values once), then new features (#39 formula variables, n = 0, native exponential), then validation and error-message changes. No entry text was dropped. README: version badge and status line to 0.5.0; the intro records that 0.5 adds formula-derived variables and the seed contract; the deferred- ideas list no longer names formula variables (they landed) and names Func:: dispatch instead. cran-comments: refresh the local-check record (simstudy now installed so the Suggests note is gone; 2 notes remain) and mention the new CI check.
# Conflicts: # NEWS.md
This was referenced Sep 24, 2026
… 0.5.0 Brings #51, #52, #59 and #61 into release prep. NEWS: the dev entries for survival dates (#40), range missing codes (#58) and the minimal-example fixture corrections are filed under the 0.5.0 categories (breaking changes, new features, validation, bug fixes) plus new Deprecations and Known issues headings; every dev bullet is present, two in the forms release prep had already rewritten, which dev had not changed since the branches split. The heading carries the provisional release date. README mentions survival dates in the 0.5 summary and feature list. cran-comments corrects the local check record: the local check library lacks simstudy (3 notes, run with _R_CHECK_FORCE_SUGGESTS_=false), while CI installs all suggested packages and reports Status: OK.
Ticks the four Task 8 items with how each was met: #38, #39 and #40 ship together with one migrating paragraph; pinned seed tests in test-seed-contract.R; R CMD check --as-cran clean on the 0.5.0 tarball and pkgdown builds; version 0.5.0, with the extension columns documented in MockData rather than in a separate downstream notice (maintainer decision, 2026-09-22).
DougManuel
marked this pull request as ready for review
September 27, 2026 11:38
Merged
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
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.
Summary
Release assembly for v0.5.0 (post-v0.4.0 plan, Task 8). It now carries everything merged into
dev(#51, #52, #59, #61) plus the release changes:DESCRIPTION:Version: 0.5.0NEWS.md: one# MockData 0.5.0 (2026-09-27)section. The [v0.5] ADR: seed and RNG-stream contract across generation stages #38, [v0.5] Formula-derived variables: ADR + phased implementation #39, [v0.5] Generate survival variable pairs inside create_mock_data() #40, simstudy backend fails for n = 0 categorical variables (pre-existing) #50 and v0.4 path fails on range-notation missing codes such as [997,999] #58 entries are filed as Breaking changes (seed contract with a Migrating paragraph, survival migration, contamination after the survival rules, the minimal example's new output, the legacy stop on anchored metadata), then New features, Validation and error messages, Bug fixes, Deprecations and Known issues (Gompertz survival parameters produce degenerate follow-up times #54, Administrative censoring date is drawn per person, not as a fixed study end date #55, Legacy survival semantics: documentation and parameter discrepancies #56). Every entry fromdevis present; the merge check confirmed none was dropped.README.md: version and status 0.5.0; the 0.5 summary and feature list mention survival dates; the deferred-ideas list namesFunc::dispatch instead of formula variables.cran-comments.md: accurate check record. Locally there are 3 notes: new submission, simstudy absent from the local check library, timestamp. CI installs all suggested packages and reportsStatus: OK. An earlier version of this file wrongly said simstudy was installed for the local check.development/post-v040-development-plan.md: Task 8 ticked, with how each item was met.Verification (local, R 4.4.2, macOS 27.0)
R CMD check --as-cran --no-manualonMockData_0.5.0.tar.gz: 0 errors, 0 warnings, 3 notes (the three incran-comments.md). The vignette rebuild passes, including all 17 survival claim assertions.pkgdown::build_site(): builds, 18 article pages; the news page shows 0.5.0.Next
After this merges into
dev, thedev → main"Release v0.5.0" PR closes the issues v0.5 resolves. Closing keywords only fire on merges intomain, so the phase PRs'Closeslines never took effect. If the release date moves from 2026-09-27, update the NEWS heading in that PR.🤖 Generated with Claude Code