Skip to content

chore(deps): update oxc-grahql-parser 0.0.6#24283

Merged
graphite-app[bot] merged 1 commit into
mainfrom
07-08-chore_deps_update_oxc-grahql-parser_0.0.6
Jul 8, 2026
Merged

chore(deps): update oxc-grahql-parser 0.0.6#24283
graphite-app[bot] merged 1 commit into
mainfrom
07-08-chore_deps_update_oxc-grahql-parser_0.0.6

Conversation

@leaysgur

@leaysgur leaysgur commented Jul 8, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

I thought there might be some code changes, but there weren't, so simply a version bump.

@leaysgur Graphite App

leaysgur commented Jul 8, 2026 •
edited
Loading

Copy link
Copy Markdown
Member Author

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

This was referenced Jul 8, 2026
Merged
Merged
@leaysgur leaysgur added the 0-merge Merge with Graphite Merge Queue label Jul 8, 2026
@leaysgur Graphite App

leaysgur commented Jul 8, 2026 •
edited by graphite-app Bot
Loading

Copy link
Copy Markdown
Member Author

Merge activity

@codspeed-hq

codspeed-hq Bot commented Jul 8, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

✅ 62 untouched benchmarks
⏩ 9 skipped benchmarks1

Comparing 07-08-chore_deps_update_oxc-grahql-parser_0.0.6 (01e5901) with main (eeb1913)2

Open in CodSpeed

Footnotes

  1. 9 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

  2. No successful run was found on 07-08-fix_formatter_css_bail_on_eof-recovered_parse_errors (229d726) during the generation of this report, so main (eeb1913) was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

@graphite-app
graphite-app Bot force-pushed the 07-08-fix_formatter_css_bail_on_eof-recovered_parse_errors branch 2 times, most recently from 4aed62e to 490c3fc Compare July 8, 2026 01:45
@graphite-app
graphite-app Bot force-pushed the 07-08-chore_deps_update_oxc-grahql-parser_0.0.6 branch from 01e5901 to ac98a2a Compare July 8, 2026 01:45
@leaysgur
leaysgur force-pushed the 07-08-chore_deps_update_oxc-grahql-parser_0.0.6 branch from ac98a2a to d592e6e Compare July 8, 2026 02:10
@leaysgur
leaysgur force-pushed the 07-08-fix_formatter_css_bail_on_eof-recovered_parse_errors branch from 490c3fc to 52c1ef3 Compare July 8, 2026 02:10
@leaysgur
chore(deps): update oxc-grahql-parser 0.0.6 (#24283)
b1d007e 
I thought there might be some code changes, but there weren't, so simply a version bump.
@graphite-app
graphite-app Bot force-pushed the 07-08-fix_formatter_css_bail_on_eof-recovered_parse_errors branch from 52c1ef3 to eeabc4a Compare July 8, 2026 02:17
@graphite-app
graphite-app Bot force-pushed the 07-08-chore_deps_update_oxc-grahql-parser_0.0.6 branch from d592e6e to b1d007e Compare July 8, 2026 02:17
Base automatically changed from 07-08-fix_formatter_css_bail_on_eof-recovered_parse_errors to main July 8, 2026 02:22
@graphite-app
graphite-app Bot merged commit b1d007e into main Jul 8, 2026
32 checks passed
@graphite-app graphite-app Bot removed the 0-merge Merge with Graphite Merge Queue label Jul 8, 2026
@graphite-app
graphite-app Bot deleted the 07-08-chore_deps_update_oxc-grahql-parser_0.0.6 branch July 8, 2026 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@leaysgur