Repository navigation
RDE-R2: release react-data-export 1.0.0-alpha.2 - #204
Merged
Merged
Conversation
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.
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-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.Commits
deps: javascript-excel ^2.0.0-alpha.3(library + playground), its own commit with a patch changeset.docProps. alpha.3's new entries (/import,/format,/render) aren't used by react-data-export.javascript-excel@2.0.0-alpha.3.release:npm run version-packagesonly, no hand edits, in pre mode (alpha).versionsynced, the playground pin bumped to1.0.0-alpha.2, the lockfile in sync, and the 2 changesets moved to.changeset/pre/.CHANGELOG
## 1.0.0-alpha.2READMEs
These are already accurate from #203, with no edit needed:
nexttag", "latestis still 0.6.0", the v0.6.0 legacy docs, the migration guide, and the "Quick path:react-data-export/legacy" paragraph/legacylineBoth are version-neutral, with no "coming" or "not yet".
docs:checkreports 11 example blocks matching.Release dry run (CI on this PR)
From
Release dry run(run 43885045092, job 133360787994):npm pack --dry-run(built package)The package now has 15 files: the main entry, the
legacyentry, and the chunk they share. The smoke test checks that the main entry reaches 2 files with no legacy code.Verification
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 merge
The
Releasejob:npm publish ./packages/react-data-export --tag next, with provenancev1.0.0-alpha.2tag and a prerelease GitHub Release