Fix: Upgrade to Gatsby v5 and Node.js v20 compatibility #3
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.
Summary
Resolves GitHub Actions build failures by upgrading Gatsby v4 to v5 for Node.js v20 compatibility.
Root Cause
The build was failing due to
lmdbpackage compilation errors with Node.js v20. The issue was V8 API incompatibility -AccessorSignaturewas removed in newer V8 versions, causing native module compilation to fail.Changes Made
gatsby-image(deprecated, replaced bygatsby-plugin-image)Test Plan
npm run build)Breaking Changes
Notes