You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dreamorosi opened this issue
Jan 17, 2025
· 0 comments
Assignees
Labels
confirmedThe scope is clear, ready for implementationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)testsPRs that add or change tests
Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered:
dreamorosi
added
confirmed
The scope is clear, ready for implementation
internal
PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
tests
PRs that add or change tests
labels
Jan 17, 2025
confirmedThe scope is clear, ready for implementationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)testsPRs that add or change tests
Summary
Vitest has released a version 3.x and the upgrade has made its way to our repo via Dependabot (#3486).
Some of the tests are failing, most likely due to changes made by the upgrade. We need to manually bump the dependency and review the tests.
Why is this needed?
So that we can keep up with the latest release and continue running tests in our CI.
Which area does this relate to?
Other
Solution
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: