Skip to content

release: react-data-export 1.0.0 - #219

Merged
securedeveloper merged 1 commit into
mainfrom
release-1.0.0
Nov 19, 2026
Merged

securedeveloper merged 1 commit into
mainfrom
release-1.0.0

Conversation

@securedeveloper

Copy link
Copy Markdown
Owner

Stable release. Merging publishes [email protected] to npm latest, which moves from 0.6.0 to 1.0.0, through release.yml (provenance, v1.0.0 tag, GitHub Release). Existing ^0.6.0 ranges keep resolving to 0.6.0; only new installs without a range get 1.0.

  • changeset pre exit + npm run version-packages: 1.0.0, .changeset/pre.json and .changeset/pre/ removed, one ## 1.0.0 section with every changeset since alpha.0.
  • Hand-written lead at the top of ## 1.0.0: what 1.0 is, then Migrating from 0.x (new API + /legacy quick path, no file-saver/tempa-xlsx, real CSV, output differences with links into docs/migration.md).
  • READMEs, docs/migration.md install line and docs/api.md status: prerelease wording removed.
  • Engine javascript-excel ^2.0.0 (Require javascript-excel ^2.0.0 #218).

Checked locally on Node 26: typecheck (incl. migration examples), build, publint, doc snippets, release-script tests (75), unit tests (185 passed, 21 skipped).

After the merge: bump the pin in react-data-export-playground.

Exit pre mode and version 1.0.0 for the latest dist-tag (from 0.6.0). The 1.0.0 changelog section opens with a summary and a 'Migrating from 0.x' lead; the READMEs, the migration guide and docs/api.md drop the prerelease wording.
@securedeveloper
securedeveloper merged commit 5287339 into main Nov 19, 2026
38 checks passed
@securedeveloper
securedeveloper deleted the release-1.0.0 branch November 19, 2026 22:28
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