Skip to content

chore: bump nearcore to 2.13.3 - #120

Closed
tropibot[bot] wants to merge 2 commits into
mainfrom
tropibot/bump-nearcore-2.13.3
Closed

chore: bump nearcore to 2.13.3#120
tropibot[bot] wants to merge 2 commits into
mainfrom
tropibot/bump-nearcore-2.13.3

Conversation

@tropibot

@tropibot tropibot Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Automated version bump triggered by release 2.13.3.

Changes

  • upstream version (near/nearcore) → 2.13.3
  • version 0.1.200.1.21
  • UPSTREAM_VERSION2.13.3

@tropibot

tropibot Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor Author

Dappnode bot has built and pinned the built packages to an IPFS node, for commit: 7083490

This is a development version and should only be installed for testing purposes.

  1. Package near.dnp.dappnode.eth

Install link

Hash: /ipfs/QmWTs37cGupaAFnjyRMrXscgfGaZJP9yANcrS4E8gyDcgi

(by dappnodebot/build-action)

@tropibot

tropibot Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Package harness completed with warnings

Both versions stabilized; advisory log analysis found a critical candidate-only signature

Package Verdict Reason Duration Cleanup
near.dnp.dappnode.eth ⚠️ Warning Candidate containers stable (candidate_containers_stable) 19m 58s ⏱️ Timed out

Run overview

Context Value
Pull request dappnode/DAppNodePackage-NEAR#120
Tested commit 70834903132e
Candidate artifact Install on DAppNode · /ipfs/QmWTs37cGupaAFnjyRMrXscgfGaZJP9yANcrS4E8gyDcgi
Baseline request automatic
Worker worker-01
Run ID gh-pr-120-70834903132e-8b17dddc8e477bad
Execution 2026-08-19T20:46:04.600856863+00:002026-08-19T21:06:02.993084576+00:00 (✅ Completed)

Baseline vs candidate

Check Baseline Candidate
Version 0.1.20 0.1.21
Install ✅ Passed · 0s ✅ Passed · 5m 32s
Hard check ✅ Passed · 5 stable samples ✅ Passed · 5 stable samples
Containers 1 observed 1 observed
Stabilization 22s 22s
Log collection ✅ Passed · 1 container ✅ Passed · 1 container

Container comparison

  • Added: none
  • Removed: none
  • Baseline inventory: DAppNodePackage-near.near.dnp.dappnode.eth
  • Candidate inventory: DAppNodePackage-near.near.dnp.dappnode.eth
  • Baseline non-running states: none
  • Candidate non-running states: none
  • Deterministic regressions: ✅ none
Container inventory

Baseline

Container Service State Image Created
DAppNodePackage-near.near.dnp.dappnode.eth near ✅ Running near.near.dnp.dappnode.eth:0.1.20 1785306301

Candidate

Container Service State Image Created
DAppNodePackage-near.near.dnp.dappnode.eth near ✅ Running near.near.dnp.dappnode.eth:0.1.21 1787172841

Runtime analysis advisory

❌ Critical — Heuristic and Nexus analysis: Candidate logs show new runtime startup/network errors not seen in baseline: ProtocolVersionMismatch handshake failure, malformed curl URL, and missing /proc/sys kernel parameter reads.

Analyzer Status Summary
Composite ❌ Critical Heuristic and Nexus analysis: Candidate logs show new runtime startup/network errors not seen in baseline: ProtocolVersionMismatch handshake failure, malformed curl URL, and missing /proc/sys kernel parameter reads.
Heuristic ✅ Clean No configured candidate-only suspicious signature was found
Nexus ❌ Critical Candidate logs show new runtime startup/network errors not seen in baseline: ProtocolVersionMismatch handshake failure, malformed curl URL, and missing /proc/sys kernel parameter reads.
Baseline evidence ✅ Clean No configured suspicious signature was found
Candidate evidence ✅ Clean No configured suspicious signature was found
Severity Container Finding Evidence
❌ Critical near Candidate neard/ping failed a network handshake due to protocol version mismatch. Baseline logs had no such error and showed healthy peers/validators, so this is a likely new connectivity regression. Error: Received Handshake Failure: ProtocolVersionMismatch { version: 86, oldest_supported_version: 83 }. Try running again with --protocol-version between 83 and 86
⚠️ Warning near Candidate startup script attempted curl with a malformed or missing URL, which was not present in baseline logs and indicates a new configuration/startup problem. curl: (3) URL using bad/illegal format or missing URL
⚠️ Warning near Candidate logs show neard::cli read failures for kernel network parameters; baseline did not show these. Missing parameters can degrade node networking and may be a new runtime regression. ERROR neard::cli: failed to read parameter param_name=net.core.rmem_max path=/proc/sys/net/core/rmem_max e=Os { code: 2, kind: NotFound, message: "No such file or directory" }; similar for net.core.wmem_max and net.core.default_qdisc

Cleanup and diagnostics

Check Result
Cleanup ⏱️ Timed out
Leftover packages none
Cleanup error target package did not return to its original version
Phase Code Message
Cleanup cleanup_failed target package did not return to its original version

Deterministic checks decide the verdict. Runtime log analysis is advisory. TropiBot publishes bounded summaries and never posts raw logs.

@tropibot tropibot Bot closed this Sep 3, 2026
@tropibot
tropibot Bot deleted the tropibot/bump-nearcore-2.13.3 branch September 3, 2026 16:00
@tropibot tropibot Bot mentioned this pull request Sep 3, 2026
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.

0 participants