fix(deps): update dependency @lezer/common to v1.2.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@lezer/common	1.0.0 -> 1.2.3

---

Release Notes

lezer-parser/common (@​lezer/common)

v1.2.3

Compare Source

Bug fixes

Fix an issue in TreeCursor.iterate that made it iterate through siblings of the current node.

v1.2.2

Compare Source

Bug fixes

Fix a bug in TreeCursor.matchContext where, if the context fell partially in a buffer node and partially in tree nodes, it could return incorrect results.

v1.2.1

Compare Source

Bug fixes

Fix a bug where getChild and getChildren would, if the first and second arguments matched the same node, return incorrect results.

v1.2.0

Compare Source

New features

The new NodeProp.isolate can be used by parser to signal that a given node should be treated as isolated when it comes to bidirectional text rendering.

v1.1.2

Compare Source

Bug fixes

Fix a crash that could happen in mixed-language parsing when mounting a tree to a zero-length node.

v1.1.1

Compare Source

Bug fixes

Fix a bug where resolveStack could sometimes yield the same node multiple times.

Allow mixed-parsing trees to be mounted for zero-length nodes.

Fix a bug in mixed-language parsing that could some parts of an inner language to be missed when incrementally reparsing from a stopped parse.

In Tree.build, when given an extremely deeply nested tree structure, flatten it instead of overflowing the stack.

v1.1.0

Compare Source

New features

The new Tree.resolveStack method returns an iterator through the nodes covering a position, including those from overlays not active at that point.

v1.0.4

Compare Source

Bug fixes

Make the package usable in TypeScript with node16/nodenext resolution.

v1.0.3

Compare Source

Bug fixes

Tree.iterate now properly includes anonymous nodes when IterMode.IncludeAnonymous is enabled.

v1.0.2

Compare Source

Bug fixes

Fix a bug in mixed parsing that would sometimes produce invalid trees.

v1.0.1

Compare Source

Bug fixes

Fix a bug that could cause incremental parsing to incorrectly reuse nodes inside nested mixed parses.

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[cr-gpt]

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables for this repo. you could follow readme for more information

[pr-codex]

Tldr

The package-lock.json files for editors/eo and editors/phi have been updated with new versions of the "@lezer/common" package (from 1.0.0 to 1.0.2).

Detailed summary

• Updated "@lezer/common" package version from 1.0.0 to 1.0.2 in package-lock.json file for editors/eo.
• Updated "@lezer/common" package version from 1.0.0 to 1.0.2 in package-lock.json file for editors/phi.

[yegor256]

@rultor please, try to merge

[rultor]

@rultor please, try to merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

[rultor]

@rultor please, try to merge

@renovate[bot] @yegor256 Oops, I failed. You can see the full log here (spent 11s)

+ set -e
+ set -o pipefail
++ dirname ./run.sh
+ cd .
+ echo 544301
+ echo '1.74.7 b768e876f'
1.74.7 b768e876f
+ date
Wed 05 Apr 2023 02:40:00 PM CEST
+ uptime
 14:40:00 up 132 days, 19:18,  0 users,  load average: 0.08, 0.02, 0.01
+ cat
com.rultor.spi.Profile: There is no 'merge' section in .rultor.yml for branch main in repo objectionary/try-phi
	at com.rultor.agents.req.StartsRequest.docker(StartsRequest.java:350)
	at com.rultor.agents.req.StartsRequest.vars(StartsRequest.java:255)
	at com.rultor.agents.req.StartsRequest.script(StartsRequest.java:148)
	at com.rultor.agents.req.StartsRequest.process(StartsRequest.java:109)
	at com.rultor.agents.AbstractAgent.execute(AbstractAgent.java:70)
	at com.rultor.spi.Agent.execute(Agent.java:84)
	at com.rultor.Routine.process(Routine.java:202)
	at com.rultor.Routine.unsafe_aroundBody0(Routine.java:180)
	at com.rultor.Routine.run(Routine.java:1)
	at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:179)
	at com.jcabi.aspects.aj.MethodInterrupter.wrap(MethodInterrupter.java:108)
	at com.rultor.Routine.unsafe(Routine.java:175)
	at com.rultor.Routine.run(Routine.java:142)
	at com.jcabi.log.VerboseRunnable.run(VerboseRunnable.java:190)
	at com.jcabi.aspects.aj.MethodScheduler.lambda./run.sh(MethodScheduler.java:194)
	at java.base/java.util.concurrent.Executors.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.run(ScheduledThreadPoolExecutor.java:305)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor.run(ThreadPoolExecutor.java:635)
	at com.jcabi.log.VerboseThreads.run(VerboseThreads.java:222)
	at java.base/java.lang.Thread.run(Thread.java:833)

+ exit -1
'cid' file is absent, most probably the Docker container wasn't started correctly