Skip to content

Bump nim-toml-serialization & nim-faststreams #7504

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: unstable
Choose a base branch
from
Open

Bump nim-toml-serialization & nim-faststreams #7504

wants to merge 1 commit into from
+2 −2

Conversation

nitely
Copy link
Contributor

@nitely nitely commented Sep 17, 2025 •
edited
Loading

@github-actions GitHub Actions
Copy link

github-actions bot commented Sep 18, 2025 •
edited
Loading

Unit Test Results

       15 files  ±0    3 020 suites  ±0   1h 27m 26s ⏱️ + 1m 54s
12 041 tests ±0  11 475 ✔️ ±0  566 💤 ±0  0 ❌ ±0 
76 316 runs  ±0  75 484 ✔️ ±0  832 💤 ±0  0 ❌ ±0 

Results for commit 188e4cf. ± Comparison against base commit b727f65.

♻️ This comment has been updated with latest results.

@nitely nitely changed the title Test nim-toml-serialization Test nim-toml-serialization & nim-faststreams Sep 25, 2025
@nitely nitely force-pushed the nitely_bump_toml_0217 branch from 8537ef8 to 80dde10 Compare September 25, 2025 18:23
@nitely nitely changed the title Test nim-toml-serialization & nim-faststreams Bump nim-toml-serialization & nim-faststreams Sep 25, 2025
@tersec
Copy link
Contributor

tersec commented Sep 28, 2025

Merge conflict on vendor/nim-toml-serialization

@nitely nitely force-pushed the nitely_bump_toml_0217 branch from 80dde10 to 188e4cf Compare September 28, 2025 06:37
@nitely nitely marked this pull request as ready for review September 28, 2025 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@nitely @tersec