-
-
Notifications
You must be signed in to change notification settings - Fork 30
Bump dependencies #217
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
Bump dependencies #217
Conversation
Co-authored-by: fregante <[email protected]>
Co-authored-by: fregante <[email protected]>
|
@copilot Tests are failing, CI is failing, dependencies (like XO) are not actually using the latest possible version |
….2.3 - Updated npm dependencies to latest: - XO: 0.60.0 → 1.2.3 (migrated to flat config) - esbuild: 0.24.2 → 0.27.2 - svelte: 5.16.0 → 5.46.1 - typescript: 5.7.3 → 5.9.3 - vite: 6.0.7 → 7.3.1 - vitest: 2.1.8 → 4.0.17 (fixes snapshot test issue) - Migrated XO config to flat config format (xo.config.js) - Fixed code style issues for new XO version - Added globals package for browser environment config Co-authored-by: fregante <[email protected]>
- Added actions/setup-node@v6 to Build job in CI workflow - Added actions/setup-node@v6 to build job in Demo workflow - Ensures correct Node version (22.18) is used in all jobs Co-authored-by: fregante <[email protected]>
Fixed all issues in commit 4fbc66d: Tests: Fixed vitest snapshot test error by updating to v4.0.17 (from incorrectly downgraded v2.1.8) Dependencies: Updated to truly latest versions:
CI: Added missing setup-node steps to CI and Demo workflows (commit 727ab91) All tests pass locally. Waiting for CI approval to complete. |
|
@copilot esm-lint.yml workflow failing |
The v7 version of download-artifact has a breaking change where it creates an extra directory level (artifact/artifact/package.json instead of artifact/package.json). Reverting to v4 fixes this issue. Co-authored-by: fregante <[email protected]>
|
@copilot Don't just downgrade it… fix the issue |
Instead of downgrading to v4, properly configure v7 by: - Adding explicit artifact name "package" to upload step - Specifying name and path parameters in all download steps - This ensures artifacts are downloaded to the correct location The v7 API requires explicit name/path configuration to avoid the extra directory level that was causing the previous failures. Co-authored-by: fregante <[email protected]>
Fixed in 98bcb2d. Now properly using
This ensures artifacts are downloaded directly to the |
toMatchInlineSnapshotbeing called multiple times at same locationSummary
Successfully updated all npm dependencies and GitHub Actions to their latest versions. The ESM lint workflow now properly uses
actions/download-artifact@v7with explicit artifact name and path configuration to ensure artifacts are downloaded to the correct location.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.