Skip to content

chore(deps): bump @openclaw/zalo from 2026.10.1 to 2026.10.2 in /plugins/zalo - #487

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/plugins/zalo/openclaw/zalo-2026.10.2
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/plugins/zalo/openclaw/zalo-2026.10.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 15, 2026

Copy link
Copy Markdown
Contributor

Bumps @openclaw/zalo from 2026.10.1 to 2026.10.2.

Release notes

Sourced from @​openclaw/zalo's releases.

openclaw 2026.10.2

2026.10.2

Highlights

Changes

  • Defaulted OpenAI and Anthropic API-key routes to provider-native compaction. (#168164) Thanks @​obviyus.
  • Reported finalized update successes and suppressed channels as warnings instead of failures. (#169037)
  • Stopped live npm dist-tag drift from failing already-validated release candidates. (#168836) Thanks @​RomneyDa.

Fixes

Complete contribution record

This audited record covers the complete v2026.10.1..64cec484d6b34d913854b6fa965635c272a1533f history: 85 in-range PRs + 0 retained seed-only PRs = 85 unique PRs. The generation manifest also supplies direct commits as editorial input; the grouped notes above prioritize user impact.

Pull requests

... (truncated)

Changelog

Sourced from @​openclaw/zalo's changelog.

Changelog

Release notes: https://docs.openclaw.ai/releases

Each release has its complete changelog below. Audited contribution records are retained separately when available.

... (truncated)

Commits
  • b8952d4 docs(changelog): refresh 2026.10.2 notes
  • 64cec48 fix(release): drop the 2026.10.5-beta.1 compat entry now that coverage is tes...
  • f18097d fix(release): make update compatibility coverage test-only (#168836)
  • 0bbffae fix(update): report finalized successes and suppressed channels as warnings (...
  • b8a93c5 test(update): pin the 2026.10.1 updater's pending-migration read after replac...
  • 14b0dd7 test(gateway): allow inert Codex code-mode probes under empty cron caps (#169...
  • 36f6305 fix(agents): keep inter-session envelopes as first-sent prompt bytes
  • 8cc1e8a fix(release): record 2026.10.5-beta.1 updater compatibility (#165539)
  • c8c785a fix(agents): subagents lose inter-session provenance in replayed history (#16...
  • 9def9c1 fix(agents): keep fallback retry prompts request-local after unprojected disp...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@openclaw/zalo](https://github.com/openclaw/openclaw) from 2026.10.1 to 2026.10.2.
- [Release notes](https://github.com/openclaw/openclaw/releases)
- [Changelog](https://github.com/openclaw/openclaw/blob/main/CHANGELOG.md)
- [Commits](openclaw/openclaw@v2026.10.1...v2026.10.2)

---
updated-dependencies:
- dependency-name: "@openclaw/zalo"
  dependency-version: 2026.10.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 15, 2026
@clawsweeper

clawsweeper Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@clawsweeper clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. labels Oct 15, 2026
@clawsweeper

clawsweeper Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

Codex review: needs changes before merge.

What this changes

This PR updates the Zalo npm fixture and lockfile from 2026.10.1 to 2026.10.2.

Example: The latest npm tag is unavailable and crabpot selects the Zalo fallback.

  • Before: The fallback selects @openclaw/zalo@2026.10.1.
  • After: The fallback selects @openclaw/zalo@2026.10.2.

Review scores

Measure Result What it means
Overall readiness 🦐 gold shrimp (3/6) Useful, tightly scoped maintenance with verified artifact contents and supporting CI, but the source-provenance mismatch needs correction.
Proof confidence 🦐 gold shrimp (3/6) This Dependabot fixture bump is outside the ordinary contributor demonstration gate; static artifact inspection verifies metadata identity, while CI success does not establish live Zalo runtime compatibility.
Patch quality 🦐 gold shrimp (3/6) 1 actionable review finding remain.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: Crabpot's Zalo fallback remains on the preceding published package version.
Reason: Keeping curated fallback artifacts current serves the repository's compatibility-testing purpose and follows established maintainer practice.

Merge readiness

⛔ Needs changes before merge - 2 items remain

Keep this PR open: main still pins 2026.10.1, and the update needs a focused source-provenance repair before merging.

Priority: P3
Reviewed head: 30e68f2ad31f9a14d81e25f1346d53bb1dd69264

Before merge

  • Update the source references alongside the Zalo version (P2) - The 2026.10.2 artifact has no gitHead, so scripts/report-lib.mjs falls back through packageEvidenceRef to fixture.source.ref once its payload version matches this new shim pin. That reference and crabpot.sourceRef still point to the 2026.10.1 build, 9cf7fc279c26cf3493b75e703aeadac6d0deb5ee, causing reports for the new artifact to cite the previous build. The npm provenance statement identifies 2040d1b71db98e8b2a5d740770c37e17f64316ba for 2026.10.2. Update both source fields together and align affected report expectations, as AGENTS.md requires.
  • Explain or restore the original intent of Zalo fixture version and published-source identity - f0a68ce: The preceding refresh intentionally paired the 2026.10.1 artifact with its published build commit and kept host compatibility limitations explicit.

Findings

  • [P2] Update the source references alongside the Zalo version — plugins/zalo/package.json:7

Provenance

  • Zalo fixture version and published-source identity changes intended behavior without addressing why it exists (f0a68ce: The preceding refresh intentionally paired the 2026.10.1 artifact with its published build commit and kept host compatibility limitations explicit.)
Agent review details

How this fits together

Crabpot acquires plugin artifacts from its fixture manifest and npm shims, inspects their contracts, and publishes compatibility reports with source links.

flowchart LR
  A[Fixture manifest] --> C[Artifact acquisition]
  B[Npm fallback pin] --> C
  C --> D[Plugin inspection]
  D --> E[Compatibility reports]
  F[Source provenance] --> E
Loading

Technical review

Best possible solution:

Update both Zalo source references to the published 2026.10.2 build commit and align affected report expectations while preserving the frozen host.

Do we have a high-confidence way to reproduce the issue?

Source inspection establishes that a 2026.10.2 payload without gitHead now matches the updated shim pin and therefore receives the old manifest source reference; no target code was executed.

Is this the best way to solve the issue?

Refreshing the fallback is consistent with prior maintainer-directed fixture updates, but package and source identity must advance together.

Full review comments:

  • [P2] Update the source references alongside the Zalo version — plugins/zalo/package.json:7
    The 2026.10.2 artifact has no gitHead, so scripts/report-lib.mjs falls back through packageEvidenceRef to fixture.source.ref once its payload version matches this new shim pin. That reference and crabpot.sourceRef still point to the 2026.10.1 build, 9cf7fc279c26cf3493b75e703aeadac6d0deb5ee, causing reports for the new artifact to cite the previous build. The npm provenance statement identifies 2040d1b71db98e8b2a5d740770c37e17f64316ba for 2026.10.2. Update both source fields together and align affected report expectations, as AGENTS.md requires.
    Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.98

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against c82f74c2c423.

Testing

Proof path: none.

Security

None.

Evidence

Acceptance criteria:

  • node --test test/manifest.test.mjs test/report-provenance.test.mjs test/sync-fixtures.test.mjs
  • node scripts/sync-fixtures.mjs --check
  • git diff --check

What I checked:

  • Pinned introduced change: The introduced diff updates only the Zalo package version, lockfile URL, integrity and peer range; current main retains 2026.10.1. (plugins/zalo/package.json:7, 30e68f2ad31f)
  • Source-link fallback consumes the stale pin: readPackagePayloadSourceRef supplies the shim version and manifest source.ref to packageEvidenceRef, which uses that ref when the artifact lacks gitHead and matches the pinned version; both Zalo source fields still contain 9cf7fc279c26cf3493b75e703aeadac6d0deb5ee. (scripts/report-lib.mjs:319, c82f74c2c423)
  • Applicable fixture policy: The complete root policy requires package-version changes to update source references and generated report/test expectations; no nested AGENTS.md or maintainer-notes directory was present. (AGENTS.md:13, 30e68f2ad31f)
  • Published artifact identity and dependency-policy signal: Crabpot explicitly acquires and inspects this plugin's executable artifact. Read-only npm inspection verified both tarball integrities: only package/package.json differs among their 867 files, with all 133 JavaScript files byte-identical. Neither artifact supplies gitHead; the 2026.10.2 npm provenance statement identifies build commit 2040d1b71db98e8b2a5d740770c37e17f64316ba. Dependency root and extensions policies were read at that commit. (extensions/zalo/package.json, 2040d1b71db9)
  • Prior maintainer refresh established the boundary: fix(fixtures): refresh eight official plugins to 2026.10.1 #461 deliberately refreshed package pins and both published-source references together, credited Dependabot, and retained the frozen 2026.9.6 host despite declared plugin API incompatibility; its maintainer discussion explicitly limited runtime qualification. (plugins/zalo/package.json:15, f0a68ce3d504)
  • Discussion, validation and history limits: The full 34,102-character PR body and both comments contain release information and review-status messages. The exact-head isolated Zalo check and fixture-lock security check passed; seven checks were still running, with no failed check reported. Some broader historical blob reads failed because lazy fetching is disabled; scoped history, available original blobs and current-main blame established the relevant ownership. (30e68f2ad31f)

Likely related people:

  • Vincent Koc: Raw commit f0a68ce adds plugins/zalo/package.json:15 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: f0a68ce3d504; files: plugins/zalo/package.json)
  • Peter Steinberger: Raw commit 3840012 adds scripts/report-provenance.mjs:3 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 384001272947; files: scripts/report-provenance.mjs)

Review metrics

Metric Value Why it matters
Published executable changes 0 of 133 JavaScript files changed The two published artifacts differ only in package metadata, limiting the runtime and supply-chain scope of this bump.

Labels

Label changes:

  • add P3: This is routine fixture maintenance with a report-provenance defect and no demonstrated new runtime failure.
  • add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🦐 gold shrimp.
  • add status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action.

Label justifications:

  • P3: This is routine fixture maintenance with a report-provenance defect and no demonstrated new runtime failure.
  • rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🦐 gold shrimp.
  • status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action.

Rating scale

6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed October 15, 2026, 5:29 AM ET / 09:29 UTC.

steipete pushed a commit that referenced this pull request Oct 15, 2026
Pair 20 official 2026.10.2 fallback package pins with published source provenance while preserving the frozen host, source-pack selectors, and compatibility gaps.

Validation: independent P0–P2 review; all 19 Linux gate stages (778 tests passed, 16 platform skips); all 20 exact fallback archives across 328 isolated execution steps; green exact-head cross-platform CI at c6cb322. Matrix and Mattermost npm proof used temporary selectors restored afterward.

Supersedes #479, #480, #481, #482, #483, #484, #485, #486, #487, #489, #490, #491, #492, #493, #495, #496, #497, #498, #499, and #500.

Co-authored-by: Vincent Koc <vincentkoc@ieee.org>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@steipete

Copy link
Copy Markdown
Contributor

Included in #501, now merged at 2a53b52. The maintainer batch pairs the package update with published source provenance and passed exact-version fallback qualification as well as required cross-platform CI. Closing this superseded dependency PR; thank you for the update.

@steipete steipete closed this Oct 15, 2026
@dependabot @github

dependabot Bot commented on behalf of github Oct 15, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/plugins/zalo/openclaw/zalo-2026.10.2 branch October 15, 2026 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant