Update detect-libc 1.0.3 → 2.1.2 (major) #19180
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ detect-libc (1.0.3 → 2.1.2) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 39 commits:
Release v2.1.2Ensure Node.js 10 and 12 can use async file-based detection methods (#33)Add semi-automated changelog #32Release v2.1.1Ensure Node.js 10 and 12 can use file-based detection methods (#30)Release v2.1.0CI: Add non-Linux integration tests for completenessPrerelease v2.1.0-rc.0CI: Publish tagged commits to npmDetect libc using the interpreter value from Node's ELF headerCI: update integration test expectationsRelease v2.0.4TypeScript: Add types field to package.json (#28)CI: remove Node.js 22CI: Add Node.js 20/22, remove CentOS (EOL)Release v2.0.3Improve getReport performance (#21)Improve filesystem-based detection of glibc (#22)CI: Latest Void Linux provides glibc 2.39CI: bump unit test actionsTests: include missing coverage in summaryCI: Update integration test environments/expectationschore: refactor by removing a couple variables (#20)Release v2.0.2Add credit for e8c0afdEnsure SPDX in header, correct grammarCI: Add tests for Node.js 20Attempt to use contents of /usr/bin/ldd file for greater performance (#19)Docs: clarify 'version numbers' refers to libc (and not this package)Add SPDX identifiers to all source code filesTest: (unit) add Node.js 18 (integration) add Fedora 38, Ubuntu 22.04Release v2.0.1CI: Switch CentOS 8 (EOL) to StreamEnsure TypeScript defs are valid, fixes initializer error (#15)Add Void Linux to integration testsRelease v2.0.0Ensure only 1 process spawned for older Node.js versionsDrop CLI, use its logic for integration tests onlyProvide async and sync API, require Node.js >= 8Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands