Repository navigation
RDE-R1: release react-data-export 1.0.0-alpha.1 - #195
Merged
Merged
Conversation
This was referenced Nov 16, 2026
securedeveloper
force-pushed
the
rde-r1-release-alpha.1
branch
from
November 16, 2026 12:20
b4e5293 to
e71a90f
Compare
securedeveloper
force-pushed
the
rde-r1-release-alpha.1
branch
from
November 16, 2026 12:24
e71a90f to
329f53b
Compare
…angelog The credit lines approved in the 1.0 triage plan (docs/triage-1.0.md, #200). A patch changeset, so the version stays 1.0.0-alpha.1.
Enter Changesets pre mode (alpha) and run `npm run version-packages`: 1.0.0-alpha.0 -> 1.0.0-alpha.1. Consumes the dataset-module and table-module changesets (minor), the CSV StrictMode fix and the community credits (patch) into packages/react-data-export/CHANGELOG.md (kept under .changeset/pre/ while in pre mode); the version constant was synced by scripts/sync-version.mjs and the playground's exact pin bumped. No hand edits. The root CHANGELOG.md (0.x history) is untouched. Merging this publishes 1.0.0-alpha.1 to npm with dist-tag next; latest stays 0.6.0.
…6.0, migration guide)
securedeveloper
force-pushed
the
rde-r1-release-alpha.1
branch
from
November 16, 2026 12:57
329f53b to
67282ae
Compare
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
RDE-R1: the release PR for react-data-export 1.0.0-alpha.1, the first 1.0 prerelease: dataset export, table export, and the CSV StrictMode fix, on javascript-excel 2.0, with the migration guide.
Release recipe (re-cut from scratch, no hand edits)
git reset --hard origin/mainat 83a33c7. That includes RDE-1.18: playground (dataset editor, live preview, <ExcelExport> and useExcelExport) #196 (playground with the Table tab), RDE-1.12: migration guide from 0.6 to 1.0 #197 (migration guide), RDE-1.9.1: CSV exports started on mount download once under StrictMode #198 (CSV fix) and RDE-1.11.1: table exports in the bundler fixtures #199 (bundler fixtures).docs/triage-1.0.md, RDE-1.13: issue and PR triage for 1.0 (done) #200) as a patch changeset in its own commit (16c93eb), so the changelog entry carries a hash.npx changeset pre enter alpha.npm run version-packages:versionexport is synced (scripts/sync-version.mjs).packages/react-data-export/package.jsonversion→ 1.0.0-alpha.1packages/react-data-export/src/index.tsexport const version = '1.0.0-alpha.1'packages/react-data-export/CHANGELOG.mdCHANGELOG.md(0.x history) is untouched.apps/playground/package.jsonreact-data-export→1.0.0-alpha.1(the exact pin, in sync)package-lock.jsonnpm ciclean).changeset/pre.json{"mode":"pre","tag":"alpha"}.changeset/*.md→.changeset/pre/*.mdCHANGELOG
Both modules (minor), plus the #198 CSV StrictMode patch and the community credits for the 8 pull requests (#143 #161 #165 #167 #171 #174 #176 #180). The credits are a patch changeset, so the version stays exactly 1.0.0-alpha.1. The handles above are inside a code block here, so this PR notifies nobody; contributors are thanked in the approved comments after the publish.
READMEs (docs commit 67282ae)
nexttag:npm install react-data-export@next", listing both modules, saying the API may still change before 1.0.0, and linking the migration guidelatestis still 0.6.0", so a plain install keeps getting 0.6.0v0.6.0tag@next) and clean break, with a direct link todocs/migration.md;lateststays 0.6.0, with thev0.6.0docs link; a dataset + table example; and a link todocs/api.md.npm run docs:checkreports "ok 10 example blocks match their files".Release dry run (CI on this PR)
From
Release dry run(run 43871284235, job 133312831829):Version changed 1.0.0-alpha.0 → 1.0.0-alpha.1, not on npm, so it would publish with
--tag next. Manual recovery is open for this version (the## 1.0.0-alpha.1section exists):release: manual run: 1.0.0-alpha.1 not on npm yet: publish with --tag next.npm pack --dry-run(built package)Verification
npm ci(Node 24.18; javascript-excel 2.0.0-alpha.2 from npm), all passing:docs:checklint:pkg(publint "All good!", attw "No problems found")esm ok 1.0.0-alpha.1 export.xlsx 3954 bytes,cjs ok 1.0.0-alpha.1 export.csv 9 bytes,types ok)Node 22/24 / React 17/18/19,Consumer TS(+ cells),Bundlers,PackandRelease dry run.On merge
The
Releasejob:npm publish ./packages/react-data-export --tag next, with provenancev1.0.0-alpha.1tag and a prerelease GitHub Release with the CHANGELOG notesIf the push run fails before publishing, run
gh workflow run release.yml --ref main.