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

chore: update backend native deps #896

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

gmaclennan
Copy link
Member

This updates the holepunch.to managed native deps to the latest versions, using the updated prebuilds.

This also changes native module prebuilds from hard-coded versions to actually use the prebuild versions that match the dependencies.

I have tested this on in an emulator to check the app loads and I can create an observation, but I have not tested beyond that.

The dependency updates are all within semver, so there should be no breaking changes, however it would be good to update comapeo-core to the same versions and check all the tests pass.

This solves issues with these modules on x64, but x64 is still blocked by better-sqlite3 which is still broken on x64.

This updates the holepunch.to managed native deps to the latest versions, using the updated prebuilds.
@gmaclennan gmaclennan self-assigned this Dec 18, 2024
@ErikSin ErikSin requested a review from achou11 January 22, 2025 18:05
@ErikSin
Copy link
Contributor

ErikSin commented Jan 22, 2025

@achou11 do you mind taking a look at this PR?

@achou11
Copy link
Member

achou11 commented Jan 22, 2025

@achou11 do you mind taking a look at this PR?

yeah I had started looking at it yesterday. My understanding is that we probably don't want to integrate this for the upcoming release just yet so I de-prioritized. Is that accurate?

EDIT: guess this could be merged into main without being part of the next release, but just a bit tedious to remember to not include this in the release branch, which is harder to do if using the release action trigger since it just uses the current state of the main branch (i think)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants