Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update module github.com/tealeg/xlsx to v3 #75

Merged
merged 3 commits into from
Jan 15, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 14, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/tealeg/xlsx v1.0.5 -> v3.3.11 age adoption passing confidence

Release Notes

tealeg/xlsx (github.com/tealeg/xlsx)

v3.3.11: 3.3.11

Compare Source

What's Changed

New Contributors

Full Changelog: tealeg/xlsx@v3.3.10...v3.3.11

v3.3.10: 3.3.10

Compare Source

What's Changed

New Contributors

Full Changelog: tealeg/xlsx@v3.3.9...v3.3.10

v3.3.9: 3.3.9

Compare Source

What's Changed

Full Changelog: tealeg/xlsx@v3.3.8...v3.3.9

v3.3.8: 3.3.8

Compare Source

What's Changed

New Contributors

Full Changelog: tealeg/xlsx@v3.3.7...v3.3.8

v3.3.7

Compare Source

Release 3.3.7

This release fixes:

  • #​788 "XLSX files produced by this library need recover by Microsoft Excel when open it."
  • #​805 "Columns seem to be numbered from 1 but documentation gives example using 0"

Note: whilst this is technically backwards compatible, if you wee using NewColForRange with a base index of 0 (instead of 1) then you'll now get a panic from the library instead of it silently doing the wrong thing and creating a file that Excel thinks is corrupt.

Full Changelog: tealeg/xlsx@v3.3.6...v3.3.7

v3.3.6: 3.3.6

Compare Source

What's Changed

New Contributors

Full Changelog: tealeg/xlsx@v3.3.5...v3.3.6

v3.3.5: 3.3.5

Compare Source

What's Changed

New Contributors

Full Changelog: tealeg/xlsx@v3.3.4...v3.3.5

v3.3.4: 3.3.4

Compare Source

What's Changed

New Contributors

Full Changelog: tealeg/xlsx@v3.3.3...v3.3.4

v3.3.3: 3.3.3

Compare Source

What's Changed

New Contributors

Full Changelog: tealeg/xlsx@v3.3.2...v3.3.3

v3.3.2: 3.3.2

Compare Source

This release fixes a bug that prevented using sub-second times in Cell.SetDateWithOptions. (Thanks @​benedictjohannes )

What's Changed

Full Changelog: tealeg/xlsx@v3.3.1...v3.3.2

v3.3.1: 3.3.1

Compare Source

What's happened since 3.3.0?

  • We revived this library - people keep using it, and keep submitting patches. I'll support them in that.
  • some concurrent testing issues were fixed and switched over to using the quicktest library inl ine with the bulk of the testing. (Thanks benedictjohannes.
  • We support go1.2.1! (Thanks egon.nijns)
  • A bunch of memory leaks have been fixed (Thanks Olivier Mengué)

v3.3.0: 3.3.0

Compare Source

Minor release comprising 18 months' worth of bug fixes and minor maintenance tasks.

What's Changed

New Contributors

Full Changelog: tealeg/xlsx@v3.2.4...v3.2.5

v3.2.4: 3.2.4

Compare Source

Captures a number of fixes since the last release, for details see here.

v3.2.3

Compare Source

This release fixes a single issue that caused panics when writing files, derived from existing files, where one or more of the existing sheets had not been visited and thus had no currentRow set on the Sheet. See issue #​644 for details.

v3.2.2

Compare Source

This release addresses critical flaws in v3.2.1 (see: https://github.com/tealeg/xlsx/milestone/14):

v3.2.1: [USE WITH CARE]

Compare Source

There are serious known bugs in this release. We're working to resolve them and a 3.2.2 will follow as soon as possible.

Issues resolved in this release - see v3.2.1 milestone :

  • Empty cells are filled by the first column name - v3.2.0 #​594
  • High memory usage while creating a xlsx file and xlsx.UseDiskVCellStore not working #​596
  • Fixes internal links #​620
  • Combine cells in the same sheet and set the droplist. Excel is damaged #​610

This release was requested as people are waiting on some of the bug fixes. All outstanding bugs for the milestone have been pushed onto the v3.3.0 milestone instead.

v3.2.0

Compare Source

This release comprises the following changes:

  • The addition of Cell.GetCoordinates() and Row.GetCoordinate() functions that fix issue #​586 .
  • #​581 allows the Row.WriteSlice method to accept slices as a target instead of just pointers to slices (the old behaviour is still supported).
  • #​582 polishes some code a little but has no external effects.

v3.1.1

Compare Source

Summary

Version 3.1.1 fixes a bug that causes cell values to be blanked (or actually be zero-value structs) when reading a sheet that contains hyperlinks. See issue #​574 .

v3.1.0

Compare Source

Summary

Version 3.1.0 fixes a number of significant issues and adds support for font strike-through, but should otherwise be 100% compatible with v3.0.0.

Changes

A full list of changes can be found here

v3.0.0

Compare Source

Summary

Version 3.0.0 of the xlsx library fixes a significant number of issues, but breaks backwards compatibility in order to do so. For a full list of changes see the milestone.

DiskV backend

You can now optionally pass the UseDiskVCellStore operation to all methods that open, or create an xlsx.File. Selecting this option will result in much lower memory usage when handling large sheets, but will run slightly slower than the default in-memory cell store backend.

Streaming support removed

If you were previously using the StreamFileBuilder you should use V2 of this library of earlier.

Sheet.ForEachRow and Row.ForEachCell accept options.

You can indicate that you'd like to SkipEmptyRows or SkipEmptyCells.

v2.0.1

Compare Source

Whoops, forgot to do a proper v2 module definition.

v2.0.0

Compare Source

This release breaks an important, but bad, assumption that there should be a 1-to-1 mapping between the cells in a sheet and the column definitions. This model simplified the development of the original library a little, but it defeats the purpose of the col definitions (to apply stylistic information over ranges of columns).

Numerous other fixes have been included. For a full list of changes look here: https://github.com/tealeg/xlsx/milestone/5?closed=1


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/github.com-tealeg-xlsx-3.x branch 2 times, most recently from b1ab35c to 4d807aa Compare January 14, 2025 12:27
@ofaurax ofaurax force-pushed the renovate/github.com-tealeg-xlsx-3.x branch from 4d807aa to 40f8416 Compare January 14, 2025 12:29
Copy link
Contributor Author

renovate bot commented Jan 14, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@ofaurax ofaurax force-pushed the renovate/github.com-tealeg-xlsx-3.x branch from 9cbabdb to 1c00c75 Compare January 14, 2025 14:01
@ofaurax ofaurax requested review from Alva8756 and DoctorVin and removed request for Alva8756 January 14, 2025 14:04
Copy link
Collaborator

@Alva8756 Alva8756 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@ofaurax ofaurax merged commit 757b084 into main Jan 15, 2025
7 checks passed
@ofaurax ofaurax deleted the renovate/github.com-tealeg-xlsx-3.x branch January 15, 2025 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants