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

Security updates from npm audit fix; shouldn't be any breaking changes #1299

Merged
merged 1 commit into from
Nov 2, 2023

Conversation

DougReeder
Copy link
Contributor

If all packages here are using semantic versioning properly, there shouldn't be any breaking changes. Do we need any testing beyond the existing testing suite?

@raucao
Copy link
Member

raucao commented Oct 28, 2023

Do we need any testing beyond the existing testing suite?

The test suite should catch any issues, but a quick smoke test in a real app never hurts.

The node 16 suite is currently failing for this PR. And I guess we should add current LTS (20.0) and perhaps 18 (still widely used) to the matrix.

@DougReeder
Copy link
Contributor Author

Smoke test completed, using Notes Together and nodeJS v16.20.2 on MacOS 14.0.

The earlier failure of the test suite was a timeout, which did not happen on a re-run.

As for nodeJS v18, both the Jaribu and Mocha tests fail with "ReferenceError: FileReader is not defined", so that will have to wait. Also note Jaribu is no longer supported

@raucao raucao merged commit 7fcafd4 into master Nov 2, 2023
3 checks passed
@raucao raucao deleted the audit-fix branch November 2, 2023 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants