Skip to content

chore: bump pkg/chipingress submodule to include batch histogram fix#2265

Draft
pkcll wants to merge 1 commit into
mainfrom
chip-ingress-batch-config-part-2
Draft

chore: bump pkg/chipingress submodule to include batch histogram fix#2265
pkcll wants to merge 1 commit into
mainfrom
chip-ingress-batch-config-part-2

Conversation

@pkcll

@pkcll pkcll commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Summary

Bump the pkg/chipingress submodule dependency in the main chainlink-common go.mod to include the histogram bucket changes that are part of the chip-ingress batch tuning work.

Intent

github.com/smartcontractkit/chainlink-common depends on its own nested module github.com/smartcontractkit/chainlink-common/pkg/chipingress. PR #2207 updates the histogram bucket boundaries in pkg/chipingress/batch/client.go. Once #2207 merges, the main module must reference the new pkg/chipingress commit so that external consumers resolve the updated package instead of the older pre-#2207 version.

Depends on

Changes

  • go.mod: bumped github.com/smartcontractkit/chainlink-common/pkg/chipingress from v0.0.11-0.20260626151909-052e55e62e62 to v0.0.11-0.20260721054349-caf610156e92
  • go.sum: updated checksums

Testing

  • make gomodtidy
  • go test ./pkg/chipingress/...

Notes

Bump github.com/smartcontractkit/chainlink-common/pkg/chipingress in the
main chainlink-common go.mod to the squashed chip-ingress-batch-config
commit (caf6101) so the main module resolves the updated chipingress
package that contains the chip_ingress.batch.request_size_* histogram
bucket changes.

This is a follow-up to #2207 and must merge after it.
@pkcll
pkcll force-pushed the chip-ingress-batch-config-part-2 branch from 9c06d68 to cf955b3 Compare July 21, 2026 05:45
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.

1 participant