chore(deps): bump oxc_semantic from 0.150.0 to 0.151.0 in /rust - #1095
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [oxc_semantic](https://github.com/oxc-project/oxc) from 0.150.0 to 0.151.0. - [Release notes](https://github.com/oxc-project/oxc/releases) - [Changelog](https://github.com/oxc-project/oxc/blob/main/CHANGELOG.md) - [Commits](oxc-project/oxc@crates_v0.150.0...crates_v0.151.0) --- updated-dependencies: - dependency-name: oxc_semantic dependency-version: 0.151.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/cargo/rust/oxc_semantic-0.151.0
branch
September 25, 2026 06:46
pull Bot
pushed a commit
to y1024/jscpd
that referenced
this pull request
Sep 25, 2026
Dependabot bumps these one crate at a time, and neither family survives that: their crates share types, so oxc_span 0.150 next to oxc_parser 0.147 fails with "expected `Span`, found a different `Span`". All four open Dependabot PRs (kucherenko#1093, kucherenko#1094, kucherenko#1095, kucherenko#1096) were red for this reason alone. cpd-tokenizer and basta were also on different oxc versions (0.147 and 0.150), so the tree carried two full copies of oxc. Both now use 0.151, and the lockfile holds one. The one API change: ParserReturn::panicked is now fatal_error, with the same meaning. The log line about OXC panicking stays as it is -- it reports a real panic caught by catch_unwind, not the field. dependabot.yml groups each family, so the next bump arrives as one PR.
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
1 participant
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.
Bumps oxc_semantic from 0.150.0 to 0.151.0.
Release notes
Sourced from oxc_semantic's releases.
Commits
bec650frelease(crates): oxc v0.151.0 (#26875)9a6dc25perf(lexer): removePunct1Ord(#26885)8be283brefactor(lexer): movepunct1_ordout ofOpMap(#26884)90eb16atest(lexer): simplifypunct1_ordtest (#26883)82dc3aarefactor(lexer): combinePairLuts::buildintoPairLuts::new(#26882)3b7cb8fperf(lexer): calculate regex keyword mask at build time (#26881)8930b86perf(lexer): convert tables checks to tests (#26880)05fdc98refactor(lexer): move helper functions below their call sites (#26879)0a61f9erefactor(lexer): move single-byte punctuation LUTs into module (#26878)65fea4erefactor(lexer): move classify LUTS into separate module (#26877)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)This change is