Skip to content

RDE-R2: release react-data-export 1.0.0-alpha.2 - #204

Merged
securedeveloper merged 2 commits into
mainfrom
rde-r2-release-alpha.2
Nov 16, 2026
Merged

securedeveloper merged 2 commits into
mainfrom
rde-r2-release-alpha.2

Conversation

@securedeveloper

@securedeveloper securedeveloper commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

Summary

RDE-R2: the release PR for react-data-export 1.0.0-alpha.2: react-data-export/legacy (the 0.x components on 1.0, deprecated) on javascript-excel ^2.0.0-alpha.3.

Merging this publishes react-data-export@1.0.0-alpha.2 to npm with dist-tag next; latest stays 0.6.0. The trusted publisher has been registered since alpha.1.

Commits

  1. da0941a, deps: javascript-excel ^2.0.0-alpha.3 (library + playground), its own commit with a patch changeset.
    • Tested on its own before the version run, against the published alpha.3: 91 tests including the cell-by-cell 0.6 goldens, smoke, publint/attw and Consumer TS 72/72, on React 17/18/19, all unchanged.
    • What changed: nothing observable. With fixed timestamps, alpha.2 and alpha.3 write byte-identical files for the same workbook (3,953 bytes, every zip part identical). The smoke sample's ±1-byte size comes from its "now" timestamp in docProps. alpha.3's new entries (/import, /format, /render) aren't used by react-data-export.
    • The tree has a single javascript-excel@2.0.0-alpha.3.
  2. af1a745, release: npm run version-packages only, no hand edits, in pre mode (alpha).
    packages/react-data-export/src/index.ts: version constant 1.0.0-alpha.1 -> 1.0.0-alpha.2
    
    • Exactly 1.0.0-alpha.2, with version synced, the playground pin bumped to 1.0.0-alpha.2, the lockfile in sync, and the 2 changesets moved to .changeset/pre/.

CHANGELOG ## 1.0.0-alpha.2

## 1.0.0-alpha.2

### Minor Changes

- 986d0d7: Add `react-data-export/legacy`, a deprecated quick path for 0.x code: `<ExcelFile>`, `<ExcelSheet>`, `<ExcelColumn>`, the 0.x default export (`import ReactExport from 'react-data-export/legacy'`), the `dataSet` shape with `xSteps`/`ySteps`, and xlsx-style cell styles, built on 1.0's export code and javascript-excel. The files it writes match 0.6.0's (checked against the real 0.6.0):
  - plain `<ExcelColumn>` headers and bold `dataSet` headers
  - 80 px default widths
  - UTC dates
  - the `Download` default name with the extension always appended
  - the `<span>` trigger wrapper
  
  0.6's bugs stay fixed:
  - one download under StrictMode
  - `fileExtension: 'csv'` writes real CSV
  - `xls`/`txt`/`html` write `.xlsx` with a warning
  - string `dataSet` columns keep their header text
  - falsy children are skipped
  
  `convertLegacyStyle` converts 0.x styles to the 1.0 style model. The entry is supported for all of 1.x and removed in 2.0, and it logs one deprecation warning in development. It's a separate entry, so the main entry's bundle doesn't include it.

### Patch Changes

- da0941a: Depend on javascript-excel `^2.0.0-alpha.3`.

READMEs

These are already accurate from #203, with no edit needed:

  • root: "1.0 prereleases are on npm's next tag", "latest is still 0.6.0", the v0.6.0 legacy docs, the migration guide, and the "Quick path: react-data-export/legacy" paragraph
  • package README: the prerelease note and a /legacy line

Both are version-neutral, with no "coming" or "not yet". docs:check reports 11 example blocks matching.

Release dry run (CI on this PR)

From Release dry run (run 43885045092, job 133360787994):

npm 11.19.1; react-data-export: HEAD 1.0.0-alpha.2, HEAD~1 1.0.0-alpha.1, npm (not published)
release: 1.0.0-alpha.1 -> 1.0.0-alpha.2, not on npm yet: publish with --tag next
+ react-data-export@1.0.0-alpha.2

npm pack --dry-run (built package)

Tarball Contents
1.1kB LICENSE
2.0kB README.md
10.9kB dist/excel-export-Bscbm4dw.cjs
9.5kB dist/excel-export-BxI14JUS.js
2.3kB dist/export-D45pCRVs.d.cts
2.3kB dist/export-D45pCRVs.d.ts
3.0kB dist/index.cjs
4.9kB dist/index.d.cts
4.9kB dist/index.d.ts
2.4kB dist/index.js
9.5kB dist/legacy.cjs
4.7kB dist/legacy.d.cts
4.7kB dist/legacy.d.ts
9.2kB dist/legacy.js
2.1kB package.json
Tarball Details
name: react-data-export
version: 1.0.0-alpha.2
filename: react-data-export-1.0.0-alpha.2.tgz
package size: 20.6 kB
unpacked size: 73.4 kB
total files: 15

The package now has 15 files: the main entry, the legacy entry, and the chunk they share. The smoke test checks that the main entry reaches 2 files with no legacy code.

Verification

  • Local (Node 26.13.1 via nvm, clean npm ci): docs:check, typecheck (library + playground + docs examples), tests (90 + the React-major guard), playground tests (10), build, publint/attw and smoke (esm ok 1.0.0-alpha.2, legacy esm ok, no legacy code in the main entry) all pass.
  • On the dependency bump: Consumer TS 72/72, and React 17 and 18 legs 91/91 with smoke.
  • CI on this PR: 37/37 pass: Node 22/24/26 × React 17/18/19, Consumer TS (+ cells), Bundlers, Pack and Release dry run.

On merge

The Release job:

  1. verifies
  2. runs npm publish ./packages/react-data-export --tag next, with provenance
  3. creates the v1.0.0-alpha.2 tag and a prerelease GitHub Release

Library and playground. Tests (91, incl. the 0.6 goldens), smoke and
Consumer TS (72/72) pass unchanged on React 17/18/19; with fixed
timestamps alpha.2 and alpha.3 write byte-identical files for our
sample. Patch changeset.
`npm run version-packages` in pre mode (alpha): 1.0.0-alpha.1 ->
1.0.0-alpha.2. Consumes the react-data-export/legacy changeset (minor)
and the javascript-excel ^2.0.0-alpha.3 dependency (patch) into
packages/react-data-export/CHANGELOG.md; the version constant was synced
by scripts/sync-version.mjs and the playground's exact pin bumped. No
hand edits.

Merging this publishes 1.0.0-alpha.2 to npm with dist-tag next;
latest stays 0.6.0.
@securedeveloper
securedeveloper merged commit 180ee54 into main Nov 16, 2026
37 checks passed
@securedeveloper
securedeveloper deleted the rde-r2-release-alpha.2 branch November 16, 2026 14:30
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