Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency nodemon to v2.0.22 #33

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 5, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
nodemon (source) 2.0.19 -> 2.0.22 age adoption passing confidence

Release Notes

remy/nodemon (nodemon)

v2.0.22

Compare Source

Bug Fixes

v2.0.21

Compare Source

Bug Fixes

v2.0.20

Compare Source

Bug Fixes
  • remove postinstall script (e099e91)

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 has been generated by Mend Renovate. View repository job log here.

@cr-gpt
Copy link

cr-gpt bot commented Apr 5, 2023

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
Copy link

pr-codex bot commented Apr 5, 2023

Tldr

The version of minimatch and nodemon have been updated in the eo and phi editors.

Detailed summary

  • The version of minimatch has been updated from 3.0.4 to 3.1.2 in both eo and phi editors.
  • The version of nodemon has been updated from 2.0.19 to 2.0.22 in both eo and phi editors.

@yegor256
Copy link
Member

yegor256 commented Apr 5, 2023

@rultor please, try to merge

@rultor
Copy link
Collaborator

rultor commented Apr 5, 2023

@rultor please, try to merge

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

@rultor
Copy link
Collaborator

rultor commented Apr 5, 2023

@rultor please, try to merge

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

+ set -e
+ set -o pipefail
++ dirname ./run.sh
+ cd .
+ echo 452135
+ echo '1.74.7 b768e876f'
1.74.7 b768e876f
+ date
Wed 05 Apr 2023 05:50:35 AM CEST
+ uptime
 05:50:35 up 132 days, 10:28,  0 users,  load average: 0.27, 0.24, 0.31
+ 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants