chore(deps): refresh project dependencies and build toolchains - #753
Merged
Conversation
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_4aa9b48c-f9e1-4f5a-9ac6-5ee872438e07) |
Contributor
Documentation previewThe documentation preview has been deployed for this pull request. |
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.
Summary
Refresh the JavaScript and Python dependency locks and the build/release toolchain to current releases.
Node remains on Active LTS Krypton and Python on 3.14. VitePress continues on the existing prerelease channel. Customized vendored C sources and the generated embedded frontend header are unchanged.
Validation
url/m3uhighlighting languages./statussuccessfully (HTTP 200).OpenWrt package builds and the remaining release architecture combinations are not exercised locally; the SDK image tags and all nine musl toolchain assets were verified.