chore(deps): take @atomichub/antelope-ship-utils 1.0.1 for a quiet connect log - #176
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR bumps @atomichub/antelope-ship-utils from 1.0.0 to 1.0.1 to reduce noisy connection logging (logging have_positions count rather than the full request payload), preventing large info-level logs in mainnet filler reconnect scenarios.
Changes:
- Update
@atomichub/antelope-ship-utilsdependency to^1.0.1inpackage.json. - Refresh
pnpm-lock.yamlto resolve and snapshot@atomichub/antelope-ship-utils@1.0.1. - Add
@atomichub/antelope-ship-utils@1.0.1tominimumReleaseAgeExcludein the workspace config.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| pnpm-workspace.yaml | Adds the new first-party version to the release-age exclusion list. |
| pnpm-lock.yaml | Updates lock entries/snapshots to @atomichub/antelope-ship-utils@1.0.1. |
| package.json | Bumps the declared dependency range to ^1.0.1. |
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…nnect log 1.0.0 logged the whole block request on every connect and reconnect, and have_positions in that request carries one 64-character id per reversible block the filler still tracks, so a mainnet filler wrote tens of kilobytes at info each time. 1.0.1 logs the count in that field instead; nothing else changes.
robrigo
force-pushed
the
chore/antelope-ship-utils-1-0-1
branch
from
August 18, 2026 00:17
a9dbe52 to
675b40b
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
1.0.0 logged the whole block request on every connect and reconnect, and
have_positionsin that request carries one 64-character id per reversible block the filler still tracks, so a mainnet filler wrote tens of kilobytes at info each time. 1.0.1 logs the count in that field instead (atomicassets/antelope-ship-utils#1); nothing else changes.Validation
pnpm install --frozen-lockfileandpnpm test(349 passing, 37 pending) on the bumped lockfile.