[Snyk] Upgrade exceljs from 4.3.0 to 4.4.0

[MHback]

Snyk has created this PR to upgrade exceljs from 4.3.0 to 4.4.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 1 version ahead of your current version.

• The recommended version was released a year ago.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gemini-code-assist]

Hello @MHback, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request upgrades the exceljs dependency from version 4.3.0 to 4.4.0. This was automatically created by Snyk. The changes include updates to package.json and yarn.lock to reflect the new version and its associated dependencies, including an upgrade to jszip from 3.5.0 to 3.10.1.

Highlights

• Dependency Upgrade: The primary change is upgrading the exceljs dependency from version 4.3.0 to 4.4.0.
• jszip Upgrade: The jszip dependency was also upgraded from version 3.5.0 to 3.10.1 as part of the exceljs upgrade.

Changelog

• package.json
  • Upgraded exceljs dependency from 4.3.0 to 4.4.0 on line 28.
• yarn.lock
  • Updated exceljs version from 4.3.0 to 4.4.0 on line 383.
  • Updated resolved exceljs URL and integrity hash on line 385.
  • Upgraded jszip dependency from 3.5.0 to 3.10.1 on line 391 and line 546.
  • Updated resolved jszip URL and integrity hash on line 548.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

A version ascends,
Old code finds a newer friend,
Bugs take their flight.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request upgrades the exceljs dependency from version 4.3.0 to 4.4.0. The changes include updates to package.json and yarn.lock files. Overall, the upgrade seems straightforward, but I have a few observations.

Merge Readiness

The pull request updates a dependency, which is generally a good practice for security and stability. However, it's crucial to ensure that the upgrade doesn't introduce any breaking changes or regressions. Since I am unable to approve the pull request, I recommend that the changes be thoroughly tested, particularly focusing on the areas of the application that use the exceljs library, before merging. Also, given that the Snyk bot created this pull request, it's important to review the Snyk report to understand any potential vulnerabilities or issues that the upgrade might address. If all tests pass and the Snyk report looks good, the pull request should be safe to merge.