chore(release): version packages - #103
Merged
Merged
Conversation
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@office-kit/xlsx@0.9.0
Minor Changes
c74f9d0Thanks @baseballyama! - Renamed the package fromxlsx-kitto@office-kit/xlsx. The oldxlsx-kitpackage on npm is deprecated and will receive no further releases — install
@office-kit/xlsxand update every subpath import (xlsx-kit/io→@office-kit/xlsx/io, and likewise for/streaming,/workbook,/worksheet,/cell,/styles,/chart,/drawing,/node, and the low-level/xml,/zip,/packaging,/schemaescape hatches). No runtime behaviour changed.Patch Changes
#102
9b1febaThanks @baseballyama! - fix:loadWorkbookrejected borders withstyle="none"(#99)Files written by OnlyOffice (and any producer that emits the explicit no-border
value) set border sides to
style="none", which is the first value ofECMA-376's
ST_BorderStyleenumeration. Loading such a file failed withexpected one of [thin, medium, ...]; got "none".noneis now accepted andround-trips faithfully; it draws no stroke in HTML/SVG preview.
#101
06dbfd8Thanks @michaelcradock76-spec! - Preserve the_xlfn.future-function prefix on read so dynamic-array formulassurvive a load → save round-trip. The reader stripped
_xlfn./_xlfn._xlws.into the model, and the writer emits formula text verbatim, so a loaded
_xlfn.SCAN(...)was written back as bareSCAN(...)— an unknown name thatExcel renders as
#NAME?. Formula text is now kept verbatim (matching openpyxl),fixing every future function (SCAN, BYCOL, LAMBDA, XLOOKUP, FILTER, SEQUENCE,
LET, ANCHORARRAY, …).