Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 17, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/dagre (source) ^0.7.47 -> ^0.7.52 age adoption passing confidence
peggy (source) ^1.2.0 -> ^4.0.3 age adoption passing confidence

Release Notes

peggyjs/peggy (peggy)

v4.0.3

Compare Source

Released: 2024-06-19

New features
  • #​509 Add and implement ES6 export button
Bug fixes
  • #​493 Allow use of an empty
    array, null, or undefined as allowedStartRules option
  • #​505 Fix vscode-eslint settings
    to work with eslint flat config
  • #​507 Remove stray semicolon in CSS
  • #​508 Fix broken text input in
    web version
  • #​512 Add "StartRules" to peg.d.ts
  • #​513 Allow whitespace between
    plucked word and its pattern.
  • #​520 Grammar with token "constructor" fails to generate
  • #​522 Switched from puppeteer
    to playwright for web tests, and added them to CI.
Documentation

v4.0.2

Compare Source

Released: 2024-02-26

Bug fixes
  • #​490 Throw error when imports are used in unsupported formats. Supported formats are now only "es" and "commonjs".
  • #​494 Updated docs to make --allowedRules * more clear
  • #​495 from-mem inadvertantly
    made the minimum supported node version v20.8. Updated to latest from-mem.

v4.0.1

Compare Source

Released: 2024-02-23

Bug fixes

v4.0.0

Compare Source

Released: 2024-02-13

Major Changes
  • #​379 Fix infinite recursion
    issue by moving reportInfiniteRecursion to the new prepare pass, and having
    it fail after finding the first issue. This will require plugin authors
    to ensure that reportInfiniteRecursion is in the new pass correctly.
  • #​417 BREAKING: change to AST to
    allow topLevelInitializer and initializer to be arrays, in support of
    multi-file inputs. This will require plugin updates. The CLI and API now
    take multiple files as input, where the first file is your main library, and
    subsequent files consist of a library of other rules. The CLI can take file
    names of the form npm:<package-name>/<filename> to load library rules from
    an NPM package that is installed relative to the previous non-npm file name,
    or to the current working directory if this is the first file name.
  • #​420 BREAKING: Node v16+ is now
    required for running the CLI or using Peggy as a library. Generated code
    still targets older runtimes.
  • #​456 BREAKING: Allow imports
    from external compiled grammars inside a source grammar, using import {rule} from "external.js". Note that this syntax will generate either
    import or require in the JavaScript output, depending on the value of
    the format parameter. This will need explicit support from
    plugins, with a few new AST node types and a few visitor changes.
  • #​463 Drop support for
    Internet Explorer. Move to eslint flat configs in order to lint minimized
    browser code for compatibility with
    defaults, maintained node versions, not op_mini all.
Minor Changes
  • #​400 Use @generated in generated
    code
  • #​404 Add support for -w/--watch
    to the command line interface.
  • #​415 Added browser key to package.json, pointing to Webpack output.
  • #​420 Updated dependencies to
    avoid audit warnings.
  • #​425 Add a pass to simplify single-character choices
  • #​427 Avoid double extraction of
    substrings in various MATCH_ bytecodes
  • #​430 Make generate-js.js ts clean
  • #​432 Add peggy.code-workspace
  • #​435 Setup tsconfig to detect use of library functions from es6 or later
  • #​436 Get rid of tsd
  • #​437 Better type checking for visitor
  • #​438 Make test build deterministic
  • #​439 Make peg$computePosDetails a little faster
  • #​440 Create directories for
    output and source-map if they do not exist, rather than erroring.
  • #​446 Add a right-associative ExponentiationExpression rule (operator **) to javascript.pegjs example grammar.
  • #​451 Make stack.js ts clean
  • #​452 Fixes to prepare generate-bytecode.js for ts-check
  • #​453 Make generate-bytecode.js ts-clean
  • #​460 Allow -t and -T testing
    from the CLI with --format es.
Bug Fixes
  • #​405 Doc example doesn't correspond to code example. From @​hildjj
  • #​415 Make docs match reality with import.
  • #​426 Fix typo in XML example.
  • #​434 Fixed bad example in docs.
  • #​445 Fix indentation in examples/javascript.pegjs.
  • #​450 Fixed misleading documentation.
  • #​466 Add docs for developers.

v3.0.2

Compare Source

Released: 2023-03-21

Minor Changes
  • #​392 Removed the --optimize
    command line argument, which has been invalid since v1.2. From @​hildjj.
Bug Fixes

v3.0.1

Compare Source

Released: 2022-03-05

Minor Changes
  • #​329 Allow plugin options in
    generate. This change loosens type checking strictness to allow for options
    unknown to Peggy, but used by plugins such as ts-pegjs. From @​hildjj.
Bug Fixes
  • #​329 Allow type definition for ParserBuildOptions to include plugin options. From @​hildjj.
  • #​346 Allow extra semicolons
    between rules. From @​hildjj.
  • #​347 Disallow '$' as an initial
    character in identifiers. This is not a breaking change because no grammar
    could have successfully used these in the past. From @​hildjj.
  • #​354 Various minor nits in the
    docs, including indentation and ensuring that the CNAME file is correct.
  • #​357 Fix infinite recursion
    possibility in repetition delimeters. From @​hildjj and @​Mingun.
  • #​359 Do not treat as many
    words as reserved. Clarify the documentation about identifiers. Ensure
    that it is more clear that the target language being generated determines
    what words are reserved. Clarify that reserved word checking is only
    done for labels. From @​nene.
  • #​364 Fix passing an incorrect
    external label to the expression inside the repeated node. From @​Mingun.

v3.0.0

Compare Source

Released: 2023-02-21

Major Changes
  • #​280 Add inline examples to
    the documentation, from @​hildjj
  • #​240 Generate SourceNodes for
    bytecode, from @​hildjj
  • #​338 BREAKING CHANGE. Update
    dependencies, causing minimum supported version of node.js to move to 14.
    Generated grammar source should still work on older node versions and some
    older browsers, but testing is currently manual for those. from @​hildjj
  • #​291: Add support for
    repetition operator expression|min .. max, delimiter|, from @​Mingun
  • #​339: BREAKING CHANGE. Updated
    the list of JavaScript reserved words. This will break existing grammars
    that use any of the new words in their rule or label names. from @​hildjj

Important information for plug-in authors: PR [#​291] added 4 new opcodes to the bytecode:

  • IF_LT
  • IF_GE
  • IF_LT_DYNAMIC
  • IF_GE_DYNAMIC

and added a new AST node and a visitor method repeated. Do not forget to update your plug-ins.

Important information for grammar authors: the following words, which used to
be valid identifiers for rules and labels, are now treated as JavaScript
reserved words, and will cause errors at compile time if you are using them:

  • abstract
  • arguments
  • as
  • async
  • boolean
  • byte
  • char
  • double
  • eval
  • final
  • float
  • from
  • get
  • goto
  • int
  • long
  • native
  • of
  • set
  • short
  • synchronized
  • throws
  • transient
  • volatile
Minor Changes
  • #​274 "*" is now a valid allowedStartRule, which means all rules are allowed, from @​hildjj
  • #​229 new CLI option
    -S <rule> or --start-rule <rule> to specify the start rule when testing,
    from @​hildjj
  • #​236 Website: show line numbers
    in parser input textarea, from @​Mingun
  • #​280 new output type
    source-with-inline-map, which generates source text with an inline map,
    from @​hildjj
  • #​285 Require that a non-empty
    string be given as a grammarSource if you are generating a source map, from
    @​hildjj
  • #​206: New output type ast and
    an --ast flag for the CLI to get an internal grammar AST for investigation
    (can be useful for plugin writers), from @​Mingun
  • #​294 Website: show errors in the
    editors, from @​Mingun
  • #​297 Website: add Discord widget,
    from @​hildjj
  • #​299 Add example grammar for a
    SemVer.org semantic version string, from @​dselman
  • #​307 Allow grammars to have
    relative offsets into their source files (e.g. if embedded in another doc),
    from @​hildjj.
  • #​308 Add support for reading test
    data from stdin using -T -, from @​hildjj.
  • #​313 Create the website using
    eleventy, from @​camcherry
Bug Fixes
  • #​283 Fix incorrect type
    information for DiagnosticCallback, from @​hildjj
  • #​287 Allow large outputs
    to be received without blocking on the CLI tests, from @​hildjj

v2.0.1

Compare Source

Released: 2022-01-01

Major Changes
  • None
Minor Changes
  • #​261: Remove documentation from
    README.md, instead linking to the HTML documentation. HTML documentation on
    https://peggyjs.org is now served from the docs branch, so that it won't
    update as we change the main branch. main must be merged onto docs as
    a part of the release process going forward.
  • #​266: Expose the private
    field problems in the Session class, from @​hildjj.
Bug Fixes
  • #​263: Broken link to unpkg.
    This bug was a symptom of a relatively bad issue in the 2.0.0 release, where
    the web version of peggy was put in the wrong place, and therefore not
    tested in the release process. From @​hildjj.

v2.0.0

Compare Source

Released: 2022-05-28

Major Changes
  • #​163: Add support for
    generating source maps, from @​Mingun
  • #​160: Introduce an API for
    reporting errors, warnings and information messages from passes. New API
    allows reporting several diagnostics at once with intermediate results
    checking after each compilation stage, from @​Mingun
  • #​218: Add a sourceMappingURL
    to the generated code, from @​hildjj
  • #​248: Remove support for
    Node.js version 10. When updating dependencies, too many of the tools we
    use no longer work on the Node 10, which went out of security maintenance
    more than a year ago. Added support for Node.js version 18, from @​hildjj
  • #​251: Make commander and
    source-map-generator full dependencies. These are not needed for the
    pre-packaged web build, but will be used by Node or people that are doing
    their own packaging for the web, from @​hildjj
Minor Changes
Bug fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes labels Jul 17, 2024
@renovate renovate bot requested a review from a team July 17, 2024 16:45
@crespocarlos
Copy link
Contributor

@elasticmachine merge upstream

@renovate
Copy link
Contributor Author

renovate bot commented Jul 22, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@crespocarlos
Copy link
Contributor

/ci

@crespocarlos
Copy link
Contributor

@elasticmachine merge upstream

@crespocarlos
Copy link
Contributor

/ci

@kibana-ci
Copy link

kibana-ci commented Jul 25, 2024

💔 Build Failed

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #22 / dashboard app - group 6 dashboard saved queries saved query management component functionality preserves the currently loaded query when the page is reloaded
  • [job] [logs] FTR Configs #22 / dashboard app - group 6 dashboard saved queries saved query management component functionality preserves the currently loaded query when the page is reloaded
  • [job] [logs] Jest Tests #13 / math(resp, panel, series) throws on actual tinymath expression errors #2
  • [job] [logs] Jest Tests #13 / math(resp, panel, series) throws on actual tinymath expression errors #2
  • [job] [logs] Jest Tests #7 / workspace_panel enzyme tests should show an error message if the expression fails to parse
  • [job] [logs] Jest Tests #7 / workspace_panel enzyme tests should show an error message if the expression fails to parse

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
canvas 1.1MB 1.1MB +309.0B
expressions 28.9KB 28.9KB +48.0B
lens 1.5MB 1.5MB +309.0B
presentationUtil 85.9KB 86.2KB +261.0B
visTypeTimelion 38.8KB 39.1KB +269.0B
total +1.2KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
expressions 99.8KB 100.1KB +261.0B
kbnUiSharedDeps-srcJs 3.2MB 3.2MB +839.0B
total +1.1KB

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@rockdaboot
Copy link
Contributor

Why is the profiling-ui team set as reviewer here? Neither peggy nor dagre are used in the Universal Profiling UI, as far as I can say. Do I miss something?

@smith smith self-assigned this Aug 5, 2024
@smith smith enabled auto-merge (squash) August 8, 2024 16:39
smith added a commit to smith/kibana that referenced this pull request Aug 8, 2024
@renovate opened elastic#188560 to update some dependencies.

The "Profiling" section in the renovate.json is not accurate:

* We don't use @types/dagre (nobody does. This must have been in profiling at some point but I have no idea.)
* peggy is used in many core, platform, and solution places and should not have profiling as the sole owner.

This removes @types/dagre and changes the name of the "Profiling" section to be "Peggy", including only peggy and owned by core and operations.
@smith
Copy link
Contributor

smith commented Aug 8, 2024

Why is the profiling-ui team set as reviewer here? Neither peggy nor dagre are used in the Universal Profiling UI, as far as I can say. Do I miss something?

@rockdaboot not sure but #190178 should take care of it.

@nuugen nuugen closed this Aug 30, 2024
auto-merge was automatically disabled August 30, 2024 08:21

Pull request was closed

@nuugen
Copy link
Member

nuugen commented Aug 30, 2024

Closing in favour of PRs to be opened by Self-Hosted Renovate.

@nuugen nuugen changed the title Update Profiling (main) Update Profiling (main) - autoclosed Aug 30, 2024
@jbudz jbudz deleted the renovate/main-profiling branch February 19, 2025 22:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

apm:review backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants