Release shinyreact 0.1.0 (npm → PyPI → CRAN)

[schloerke]

Release chain for the three packages, from branch schloerke/rc-v0.1.0-release-chain (Conductor renamed it). Process: /release-shinyreact (.claude/skills/release-shinyreact/, #284). Order matters: the Python and R packages vendor the built JS, and examples/09-hmr depends on the published npm client, so npm goes first; CRAN is slowest, so it goes last.

0. Prepare the rc-v0.1.0 branch (all packages)

• git pull / rebase on main
• Version bumps: pkg-r/DESCRIPTION → 0.1.0, pkg-js/package.json → 0.1.1 (published), pyproject.toml already 0.1.0
• make update-dist and make update-examples and make update-skills, confirm no drift
• make js-lint && make js-format-check && cd pkg-js && npx vitest run
• make py-check and make py-check-tox
• make r-check
• make py-test-e2e
• Confirm protocol/README.md version (1.0) matches config.ts, _protocol.py, protocol.R (parity test)
• Write release notes: pkg-r/NEWS.md, pkg-py/CHANGELOG.md, pkg-js/CHANGELOG.md (first release: summarize the ui.tsx pattern surface)
• Merge chore: release prep for 0.1.0 #309 (schloerke/rc-v0.1.0-release-chain → main) once pr-done is green

1. npm: @posit-dev/shinyreact 0.1.1 — released 2026-09-12 ✅

• NPM_TOKEN repository secret exists (Add NPM_TOKEN secret for @posit/shinyreact publishing #218)
• cd pkg-js && npm run build && npm pack --dry-run and inspect the tarball contents (dist-npm/ only)
• Tag js/v0.1.1 on the merge commit and push; release-js.yaml publishes with provenance
• Verify npm view @posit/shinyreact version
• Examples depend on the published @posit-dev/shinyreact@^0.1.1 (refactor: rename npm package to @posit-dev/shinyreact #297 rename, refactor(examples): depend on the published @posit-dev/shinyreact #307 switch)

2. PyPI: shinyreact 0.1.0

• shiny 1.8.0 (py-shiny#2475) is on PyPI; pyproject.toml requires shiny>=1.8.0, git dep and allow-direct-references dropped (chore: release prep for 0.1.0 #309)
• Registered a pending trusted publisher on PyPI: repo posit-dev/shinyreact, workflow release-py.yaml, environment (Any) (the workflow runs in the GitHub pypi environment)
• uv build locally and inspect the wheel (www/ and .agents/skills/ included; twine check passes; sdist trimmed to the Python package; readme/license/URLs metadata in build(py): PyPI metadata for the first release #310)
• py/v0.1.0 tagged at c94ae9b; release-py.yaml run 34730067807 published https://pypi.org/project/shinyreact/0.1.0/ (wheel + sdist, Requires-Dist: shiny>=1.8.0, htmltools>=0.7.0) and created the Python v0.1.0 GitHub release with attestations
• Verified: clean uv venv + uv pip install shinyreact==0.1.0 resolves shiny 1.8.0; shiny run examples/01-hello/app.py serves shinyreact-0.1.1/shinyreact.js, ui.js, and the #shinyreact-config tag

3. CRAN: shinyreact 0.1.0

First release:

• pkg-r/NEWS.md (chore: release prep for 0.1.0 #309), tidyverse-style polish (docs(r): polish NEWS.md for 0.1.0 #314)
• pkg-r/cran-comments.md (chore(r): CRAN prep for 0.1.0 #311); 0 notes after the wording fix in chore(r): reword Title/Description to clear the win-builder spelling NOTE #313
• README: install.packages("shinyreact") first, GitHub dev install second (chore(r): CRAN prep for 0.1.0 #311)
• Title/Description: 'Shiny' and 'React' single-quoted, react.dev linked (chore(r): CRAN prep for 0.1.0 #311)
• All 7 exports have @return; @examples added to the 6 that lacked them (chore(r): CRAN prep for 0.1.0 #311)
• Authors@R: Posit Software, PBC (cph, fnd) and Meta Platforms, Inc. (cph, bundled React)
• Bundled JS licensing: only Meta copyright headers in the bundle (React/ReactDOM, MIT); Meta added as cph, noted in cran-comments.md. shiny-react is Posit's own (chore(r): CRAN prep for 0.1.0 #311)
• extrachecks: grep sweep clean (T/F, \dontrun, .GlobalEnv, http://); full pass through posit-dev/skills r-lib/cran-extrachecks checklist in chore(r): CRAN prep for 0.1.0 #311 (Title 59 chars + title case, 4-sentence Description with UI expanded, no commented-out example code, no relative README links, LICENSE year 2026, method-references note in cran-comments.md)

Prepare for release:

• urlchecker::url_check(): all 20 URLs correct
• devtools::check(remote = TRUE, manual = TRUE): 0 errors, 0 warnings, 1 note (New submission); make r-check Status OK, 325 tests. Local machine has no pdflatex, so the PDF manual was not built — win-devel covers it
• devtools::check_win_devel() submitted from chore(r): CRAN prep for 0.1.0 #311's tree (merged as d2a90f0); result: 1 NOTE (New submission; "possibly misspelled" UI, renderer). Fixed the wording instead: Title is now Client-Side 'React' Interface for 'Shiny', Description says "user interface" / "render function" (chore(r): reword Title/Description to clear the win-builder spelling NOTE #313)
• Draft blog post

Submit to CRAN:

• Version is already 0.1.0 (chore: release prep for 0.1.0 #309); no bump needed
• Submitted shinyreact 0.1.0 to CRAN from main 8e13be8 (2026-09-13); "Package submission successful"
• Approve email

Wait for CRAN...

• Accepted 🎉
• Finish & publish blog post
• Add link to blog post in pkgdown news menu
• usethis::use_github_release()
• usethis::use_dev_version(push = TRUE)
• usethis::use_news_md()
• Share on social media
• Slack link to blog post, bluesky, and linkedin in #open-source-comms

4. After all three

• Bump dev versions: pyproject.toml → 0.1.1.dev0
• Close Add NPM_TOKEN secret for @posit/shinyreact publishing #218 and update Publish a GitHub release with WebAssembly assets so shinylive can install shinyreact #268 as applicable