⬆️ upgrade low risk dependencies to their newest minor version#5025
⬆️ upgrade low risk dependencies to their newest minor version#5025matt-fidd merged 23 commits intoactualbudget:masterfrom
Conversation
actual-github-bot
bot
changed the title
✅ Deploy Preview for actualbudget ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Bundle Stats — desktop-clientHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger
Smaller No assets were smaller Unchanged
|
Bundle Stats — loot-coreHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller
Unchanged No assets were unchanged |
matt-fidd
changed the title
matt-fidd
changed the title
## Walkthrough
This pull request updates various development and runtime dependencies across multiple package.json files in the repository, including upgrades to packages such as vitest, better-sqlite3, eslint, and several others. Additionally, it updates the Playwright Docker container image version used in GitHub Actions workflows for end-to-end and visual regression testing from v1.41.1-jammy to v1.52.0-jammy. A SCSS file was also modified to replace an `@import` directive with `@use` for a font package. No changes were made to the structure, scripts, or exported entities in any of the affected files; all modifications are limited to dependency and container image version bumps and a minor SCSS syntax update.
## Possibly related PRs
- actualbudget/actual#3987: Also updates the better-sqlite3 dependency but from an earlier version range, related by dependency version management.
- actualbudget/actual#4856: Upgrades vitest and involves Playwright-related testing changes, related through testing dependencies though with different scopes.
- actualbudget/actual#4674: Adds Playwright-based testing infrastructure and workflows, related by Playwright usage though not overlapping in version bumps.
## Suggested reviewers
- MikesGlitchNote ⚡️ AI Code Reviews for VS Code, Cursor, WindsurfCodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback. Note ⚡️ Faster reviews with cachingCodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 30th. To opt out, configure Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
/update-vrt just in case! |
|
@coderabbitai are you able to collect the changes from the release notes of all of the packages I've bumped and post them here? |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain@matt-fidd Absolutely! I'll collect the release notes for all the packages you've bumped. Let me gather that information for you. 🌐 Web query: 💡 Result: Based on the search results, I can provide information about the changelog for better-sqlite3 from version 11.9.1 to version 11.10.0. The latest version of better-sqlite3 is 11.10.0, which was released on May 8, 2025, approximately 10 days before the current date[1]. This update follows version 11.9.1[4]. While the search results don't provide a comprehensive changelog specifically for the 11.9.1 to 11.10.0 update, we can see from the GitHub releases page that there is a full changelog available at the repository with the link path "v11.9.1...v11.10.0"[4]. The repository mentions that the changes included addressing issues referenced in PR #1357[4]. Unfortunately, the detailed list of changes in this particular version update isn't fully captured in the search results. Based on the pattern of previous updates, the release likely includes bug fixes, performance improvements, or feature enhancements. The library maintains its position as "the fastest and simplest library for SQLite in Node.js"[1]. It's worth noting that better-sqlite3 version 11.10.0 supports Node.js LTS v22.x.x, resolving previous compatibility issues that existed in earlier versions[8]. This is significant as earlier versions (11.x.x and earlier) had issues with Node.js LTS v22.x.x, causing "Could not locate the bindings file" errors[8]. If you need the complete and detailed changelog, you would need to visit the GitHub repository directly to view the full commit history between these two versions. Citations:
🌐 Web query: 💡 Result: @playwright/test Changelog: 1.41.2 to 1.52.0Below is a summary of the most significant changes and highlights introduced in @playwright/test from version 1.41.2 up to 1.52.0. Version 1.52.0 (Latest)Highlights:
Key Additions and Changes (v1.41.2 — v1.52.0)
General Capabilities (For Reference)
Notable Browser Updates
Sources:
[1] Citations:
🌐 Web query: 💡 Result: Vitest Changelog: v3.0.9 → v3.1.3Below is a summary of the significant changes, enhancements, and fixes in Vitest from version 3.0.9 to 3.1.3, based on the official GitHub release notes and migration guides. v3.1.3 (Latest as of May 2025)
v3.1.2 – v3.1.1 v3.1.1
v3.1.0 (including betas)
v3.0.9
Additional Notable Changes and Migration NotesFrom the Migration Guide[5]:
Summary Table
For complete details, consult the [Vitest GitHub releases page][1] and the official [Migration Guide][5]. Citations:
🌐 Web query: 💡 Result: The Version 3.13.0 (2020-06-01):
Version 3.14.0 (2020-07-28):
Version 3.15.0 (2020-08-25):
Version 3.16.0 (2020-09-15):
Version 3.17.0 (2020-10-13):
Version 3.18.0 (2020-11-10):
Version 3.19.0 (2021-01-05):
Version 3.20.0 (2021-02-09):
Version 3.21.0 (2021-03-09):
For a comprehensive list of changes, including minor updates and bug fixes, you can refer to the official GitHub repository's release notes. (github.com) Citations: 🌐 Web query: 💡 Result: I'd like to provide you with information about the changelog for i18next from version 23.11.5 to 23.16.8. Based on the available information, here are the relevant changes that occurred between these versions: Version 23.16.8This appears to be one of the more recent releases, with the changelog mentioning:
Version 23.7.20While not in the exact range you requested, this is one of the documented versions after 23.7:
Version 23.7.19
Version 23.7.18
Version 23.7.16
It's worth noting that there appears to be a gap in the documented changelog between 23.7.20 and 23.16.8 in the search results provided. The most recent versions mentioned in the search results are:
There was also an issue in a GitHub repository about upgrading i18next from 21.10.0 to 23.11.5 dated April 27, 2024[9], but it doesn't contain specific changelog information for the versions you're asking about. For the most comprehensive and up-to-date changelog information, I would recommend checking the official GitHub repository for i18next or their documentation website directly. Citations:
🌐 Web query: 💡 Result: Sass Changelog: 1.70.0 to 1.89.0Below is a summary of the notable changes, breaking changes, deprecations, bug fixes, and enhancements in Dart Sass (the reference implementation for the Sass language) from version 1.70.0 up to 1.89.0. 1.70.0
1.79.x to 1.80.0
1.83.x to 1.85.0
1.86.x to 1.88.0
1.89.0 (Latest as of May 2025)
Important Highlights and Breaking Changes
Deprecation Guidance
Summary From 1.70.0 to 1.89.0, Dart Sass saw the formal deprecation of legacy import and function APIs in favor of its module system, performance and correctness improvements in selector and color logic, expanded API options, and multiple bug fixes focused on standards compliance and cross-environment predictability[1][3][5]. For detailed release-by-release change logs, consult the full Dart Sass CHANGELOG[3] or the GitHub releases page[1]. Citations:
🌐 Web query: 💡 Result: Based on the search results, I can provide information about the changes between lru-cache versions 11.0.2 and 11.1.0. The lru-cache package is a popular Node.js caching implementation that deletes the least-recently-used items when the cache reaches its limit. Version 11.1.0 was released after version 11.0.2, with both versions being relatively recent releases in 2024-2025. Looking at the available information, the main package-lock.json shows the current version is 11.1.0[9]. While the search results don't provide a detailed changelog specifically for the transition from 11.0.2 to 11.1.0, we can see that various GitHub workflow runs show the progression of versions, including 11.0.1, 11.0.2, and then 11.1.0[5][7]. The package supports a wide range of features, including:
There was a transition from version 10.x.x to version 11.0.0 around July 8, 2024[7], and then subsequent minor releases within the 11.x branch. The most recent published version according to npm is 11.1.0, which was released approximately 2 months before the current date[4]. While the specific changes between 11.0.2 and 11.1.0 aren't detailed in the search results, the package has maintained its core functionality as a cache that deletes the least-recently-used items when configured limits are reached. For the most detailed and accurate information about specific changes between these versions, you would need to check the full CHANGELOG.md on GitHub which is referenced but not fully provided in the search results[2]. Citations:
🌐 Web query: 💡 Result: The Version 5.4.3 (July 6, 2023):
Version 5.4.2 (April 25, 2023):
Version 5.4.1 (April 21, 2023):
Version 5.4.0 (February 5, 2023):
Version 5.3.4 (February 2, 2023):
Version 5.3.3 (February 2, 2023):
Version 5.3.2 (January 20, 2023):
Version 5.3.1 (November 28, 2022):
Version 5.3.0 (November 9, 2022):
Version 5.2.1 (October 20, 2022):
Version 5.2.0 (October 19, 2022):
Version 5.1.10 (September 28, 2022):
Version 5.1.9 (August 23, 2022):
Version 5.1.8 (July 4, 2022):
Version 5.1.7 (June 25, 2022):
Version 5.1.6 (May 10, 2022):
Version 5.1.5 (April 14, 2022):
Version 5.1.4 (March 4, 2022):
Version 5.1.3 (February 3, 2022):
Version 5.1.2 (January 13, 2022):
Version 5.1.1 (December 20, 2021):
Version 5.1.0 (December 3, 2021):
For a comprehensive list of changes, you can refer to the official changelog. 🌐 Web query: 💡 Result: Chokidar version 3.6.0 introduced several key updates over version 3.5.3:
For a comprehensive list of changes, you can refer to the full changelog on GitHub. (github.com) Citations:
🌐 Web query: 💡 Result: Based on the search results, I can provide information about the changes between memfs versions 3.5.3 and 3.6.0. Looking at the changelog for memfs, version 3.6.0 was released on June 16, 2023, while version 3.5.3 was released on June 7, 2023[1][4]. Unfortunately, the search results don't provide the specific changes introduced in version 3.6.0 compared to 3.5.3. The changelog shown in the search results jumps from version 3.5.3 directly to version 4.1.0 without detailing the specific changes in version 3.6.0[1]. There is only a brief mention that version 3.6.0 included "node fs and volume improvements (5bc245b)"[1]. If you need more detailed information about the specific changes between these versions, you might need to check the full changelog on the memfs GitHub repository or look at the specific commit referenced (5bc245b). Citations:
🌐 Web query: 💡 Result: Between versions 3.15.1 and 3.23.2 of fast-check, several notable updates were introduced: Version 3.23.2 (December 13, 2024):
Version 3.23.1 (November 3, 2024):
Version 3.23.0 (November 1, 2024):
For a comprehensive list of changes, you can refer to the full changelog on GitHub. (github.com) Citations: @matt-fidd Here's a compilation of the release notes for all the packages you've upgraded in this PR: better-sqlite3: 11.9.1 → 11.10.0
@playwright/test: 1.41.2 → 1.52.0
vitest: 3.0.9 → 3.1.3v3.1.0 - v3.1.3
google-protobuf: 3.12.4 → 3.21.4Multiple major and minor version bumps with improvements across C++, Java, and Python implementations, including:
i18next: 23.11.5 → 23.16.8
sass: 1.70.0 → 1.89.0Key Changes
lru-cache: 11.0.2 → 11.1.0
openid-client: 5.4.3 → 5.7.1
chokidar: 3.5.3 → 3.6.0
memfs: 3.5.3 → 3.6.0
fast-check: 3.15.1 → 3.23.2Notable Changes
Would you like me to dive deeper into any specific package's changes? |
matt-fidd
force-pushed
the
deps-minor
branch
2 times, most recently
from
da19f75 to
fd98378
Compare
|
/update-vrt |
matt-fidd
changed the title
matt-fidd
force-pushed
the
deps-minor
branch
2 times, most recently
from
bbed544 to
5f928e3
Compare
matt-fidd
force-pushed
the
deps-minor
branch
4 times, most recently
from
f7810ff to
a649fc2
Compare
matt-fidd
changed the title
2 participants
This gets all of the lower risk (not react, webpack, babel, redux, electron related) deps up to their newest minor version.