Repository navigation
release: javascript-excel 2.0.0-alpha.4 - #101
Merged
Merged
Conversation
`npm run version-packages` in pre mode (alpha): 2.0.0-alpha.3 -> 2.0.0-alpha.4. Consumes the JSE-21 changeset (unmapped schema fields are null in every row) into the package CHANGELOG (kept under .changeset/pre/ while in pre mode). The VERSION constant was synced by scripts/sync-version.mjs and the private workspaces' pins follow; no hand edits. OPS-11 (CI/dev only) had no changeset. Merging this publishes 2.0.0-alpha.4 to npm with dist-tag next.
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.
JSE-R4: the release PR for javascript-excel 2.0.0-alpha.4. Merging publishes it to npm on
nextthrough trusted publishing, then tagsv2.0.0-alpha.4and creates a GitHub Release from the CHANGELOG section.How it was cut
npm run version-packagesonmainat a0a9741, in pre mode (alpha), with no hand edits:changeset version: 2.0.0-alpha.3 → 2.0.0-alpha.4. It writes the## 2.0.0-alpha.4CHANGELOG section and moves the consumed changeset to.changeset/pre/.scripts/sync-version.mjs:VERSIONinsrc/index.tsis"2.0.0-alpha.4".What's in alpha.4
importDataset/applyMapping: a schema field without a column isnullin every row, andcolumnslists every schema field (unmapped:type: 'empty', empty title and letter)OPS-11 (#99, the dependency guard and the
examples/nodedeclaration) was CI and dev only, with no changeset, so it has no CHANGELOG entry.Checks
package.jsonandVERSIONare both exactly2.0.0-alpha.4.scripts/release-check.mjs, run locally on this commit): "release: 2.0.0-alpha.3 -> 2.0.0-alpha.4, not on npm yet: publish with --tag next". The PR'sRelease dry runjob runsnpm publish --dry-run --tag next.After the publish, react-data-import #13 raises its floor to
^2.0.0-alpha.4and comes out of draft.