Repository navigation
chore(frontend-promql): bump promql-parser to the upstream v0.11.1 sync - #1184
Merged
Merged
Conversation
ProjectASAP/promql-parser#10 merged upstream GreptimeTeam v0.11.1: integral and start_timestamp parse, first_over_time is no longer experimental, and the lexer no longer recurses (stack overflow fix). Newly parsed functions stay unsupported until the lowerer maps them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Bumps the
promql-parserpin incrates/frontend-promql/Cargo.tomlfrom9fede7eto1d1562e, the merge of ProjectASAP/promql-parser#10. That PR synced upstream GreptimeTeam v0.11.1:integralandstart_timestampnow parse (both experimental upstream);first_over_timeis no longer experimental.distinct_over_time,entropy_over_time,l2_over_time) are kept.As the comment on the pin says, newly parsed functions stay unsupported until the lowerer gives them a mapping, so planning behaviour shouldn't change.
Cargo.lockalso picks up the parser's own dependency bumps from upstream: grmtools (lrlex/lrpar/cfgrammar) 0.13 → 0.14 andbincode1 → 2. Nothing else in the workspace changes.Tested: before #10 merged, the
asap-frontend-promqlandasap-frontend-metricsqltests passed against the sync branch via a local[patch]. Against currentmain, CI is the check.🤖 Generated with Claude Code