Repository navigation
build: pin @kaciras/deasync to 1.1.0 - #16328
Merged
Merged
Conversation
Signed-off-by: Aryan Sharma <aryansharma24106@gmail.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Planeshifter
pushed a commit
that referenced
this pull request
Oct 27, 2026
Ports the fix from #16328 to resolve the CI dependency installation failure (`binding.gyp not found` when building `@kaciras/deasync`). No-op once the base branch carries the same change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017wWD7ArgTRGJD2J6DitJ2W
4 of 7 tasks
Planeshifter
pushed a commit
that referenced
this pull request
Oct 27, 2026
Ports the fix from #16328 to resolve the CI dependency installation failure (`binding.gyp not found` when building `@kaciras/deasync`). No-op once the base branch carries the same change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017wWD78YjA2bMx3817c7htZ
4 of 7 tasks
Planeshifter
pushed a commit
that referenced
this pull request
Oct 27, 2026
Port of #16328. CI `npm install` currently fails building `@kaciras/deasync` (`binding.gyp not found`), breaking `Lint PR title` and other install-dependent jobs. This change no-ops once the base branch carries the same pin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017wWD77jkABgfoQzdCbeSyY
4 of 7 tasks
@kaciras/deasync to 1.1.0
Planeshifter
approved these changes
Oct 28, 2026
Planeshifter
left a comment
Member
There was a problem hiding this comment.
Thank you!
Pinning to 1.1.0 since that version was published more than two years ago. Broken release is 1.2.0.
Filed an issue to get this fixed upstream in the dependency: Kaciras/deasync#1
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.
Description
This pull request:
@kaciras/deasyncstrictly to1.1.0inpackage.jsonandetc/npm/deps.txt. Recently, version1.2.0was published upstream with a missingbinding.gypfile, causingmake install-node-modulesto fail globally across all PRs. This PR removes the caret (^1.0.1) to act as a hotfix and unblock all CI pipelines.Related Issues
This pull request has the following related issues:
Reference Packages
This pull request followed these packages:
Questions
No.
Other
Once the upstream package publishes a working patch, we can revert this and restore the caret range.
Checklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
I consulted LLMs to analyze the global CI failure logs, inspect the repository's dependency tree, and trace the issue back to the newly published
@kaciras/deasync@1.2.0upstream release. Codex updated the dependency pins to1.1.0and corrected the PR title and description to identify1.2.0as the broken release.@stdlib-js/reviewers