Skip to content

chore(ci): nim-libp2p master auto bump #7014

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

Draft
wants to merge 1 commit into
base: unstable
Choose a base branch
from

Conversation

richard-ramos
Copy link
Member

This PR just exists to allow CI to run, should not be merged / closed

EDIT: CI job executing the auto-bump for reference: https://github.com/vacp2p/nim-libp2p/actions/workflows/dependencies.yml

Copy link

github-actions bot commented Mar 13, 2025

Unit Test Results

       15 files  ±0    2 650 suites  ±0   1h 27m 28s ⏱️ + 11m 14s
  6 628 tests ±0    6 070 ✔️ ±0  558 💤 ±0  0 ±0 
45 646 runs  ±0  44 864 ✔️ ±0  782 💤 ±0  0 ±0 

Results for commit 497239a. ± Comparison against base commit 2a77820.

♻️ This comment has been updated with latest results.

@status-im-auto status-im-auto force-pushed the nim-libp2p-auto-bump-unstable branch 5 times, most recently from cbcc340 to 58657b8 Compare March 17, 2025 13:09
@jakubgs jakubgs force-pushed the nim-libp2p-auto-bump-unstable branch from 58657b8 to c578b16 Compare May 4, 2025 19:30
@jakubgs
Copy link
Member

jakubgs commented May 4, 2025

This branch has not been updated in two months. I have updated it manually since we need mainnet nodes to work.

All jobs are failing: https://github.com/vacp2p/nim-libp2p/actions/workflows/dependencies.yml

@jakubgs
Copy link
Member

jakubgs commented May 19, 2025

I tried again bumping nim-libp2p-auto-bump-unstable branch manually since CI seems broken:

But it fails to build:

.../vendor/nim-libp2p/libp2p/transports/quictransport.nim(4, 11) Error: cannot open file: pkg/quic

Since the new versions haven't been integrated yet.

@status-im-auto status-im-auto force-pushed the nim-libp2p-auto-bump-unstable branch 14 times, most recently from 8e2ef84 to 882a6b7 Compare June 3, 2025 14:18
@status-im-auto status-im-auto force-pushed the nim-libp2p-auto-bump-unstable branch 2 times, most recently from f036023 to de03da7 Compare June 6, 2025 10:28
@status-im-auto status-im-auto force-pushed the nim-libp2p-auto-bump-unstable branch 14 times, most recently from 0a78f28 to ea2ca8e Compare July 24, 2025 19:52
@etan-status etan-status force-pushed the unstable branch 3 times, most recently from a0510ce to aa88cd4 Compare July 25, 2025 15:05
@status-im-auto status-im-auto force-pushed the nim-libp2p-auto-bump-unstable branch 9 times, most recently from 8bcea9c to 5176430 Compare August 1, 2025 07:34
@status-im-auto status-im-auto force-pushed the nim-libp2p-auto-bump-unstable branch 2 times, most recently from acb8fe5 to 6aab32f Compare August 5, 2025 14:00
@status-im-auto status-im-auto force-pushed the nim-libp2p-auto-bump-unstable branch from 6aab32f to 497239a Compare August 6, 2025 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants