Skip to content

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

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

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.


Bumps @openclaw/msteams from 2026.10.1 to 2026.10.2.

Release notes

Sourced from @​openclaw/msteams'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/msteams'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/msteams](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/msteams"
  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 P2 Normal priority bug or improvement with limited blast radius. 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 MSteams fixture’s fallback npm dependency from 2026.10.1 to 2026.10.2.

Example: The npm latest tag cannot be resolved during MSteams fixture materialization.

  • Before: Crabpot falls back to @openclaw/msteams@2026.10.1.
  • After: Crabpot falls back to @openclaw/msteams@2026.10.2.

Review scores

Measure Result What it means
Overall readiness 🦐 gold shrimp (3/6) Useful, focused maintenance with one concrete report-provenance defect.
Proof confidence 🌊 off-meta tidepool Not applicable: This Dependabot maintenance PR is outside the ordinary contributor proof gate; passing isolated-fixture CI supports validation but does not establish live Teams 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 fallback fixture otherwise remains on the previous published MSteams release.
Reason: Tracking official plugin releases is an established fixture-maintenance purpose, with prior maintainer updates preserving the same host and acquisition model.

Merge readiness

⛔ Needs changes before merge - 2 items remain

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

Priority: P2
Reviewed head: 0b824fdb5220a43774b0da0e42b00be52f279fa6

Before merge

  • [P2] Advance both source references with the npm artifact (P2) - When Crabpot inspects @openclaw/msteams@2026.10.2, both the artifact and registry lack gitHead. scripts/report-lib.mjs therefore falls back to fixture.source.ref because the payload version now matches this pin. The manifest and shim still name 9cf7fc279c26cf3493b75e703aeadac6d0deb5ee, so reports attribute the new artifact to the previous build. npm provenance identifies 2040d1b71db98e8b2a5d740770c37e17f64316ba as the new build commit. Update crabpot.config.json and crabpot.sourceRef in this shim together, as docs/operations.md requires.
  • Explain or restore the original intent of MSteams fallback artifact and source identity - f0a68ce: The prior merged update paired fallback package locks with their published build references while preserving the frozen host and moving plugin tracks.

Findings

  • [P2] [P2] Advance both source references with the npm artifact — plugins/msteams/package.json:7

Provenance

  • MSteams fallback artifact and source identity changes intended behavior without addressing why it exists (f0a68ce: The prior merged update paired fallback package locks with their published build references while preserving the frozen host and moving plugin tracks.)
Agent review details

How this fits together

Crabpot resolves fixture packages from its manifest and npm shims, materializes their artifacts, and produces compatibility reports with source links.

flowchart LR
  A[Fixture manifest] --> C[Package resolution]
  B[Npm fallback pin] --> C
  C --> D[Materialized MSteams artifact]
  D --> E[Compatibility inspection]
  E --> F[Reports and source links]
Loading

Technical review

Best possible solution:

Update both MSteams source references to the published 2026.10.2 build commit alongside the dependency pin.

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

The artifact has no gitHead, and source inspection shows its new matching version selects the retained old source reference; no target code was executed.

Is this the best way to solve the issue?

The package and lockfile update is appropriately scoped, but its source metadata must advance with the artifact to preserve trustworthy reports.

Full review comments:

  • [P2] [P2] Advance both source references with the npm artifact — plugins/msteams/package.json:7
    When Crabpot inspects @openclaw/msteams@2026.10.2, both the artifact and registry lack gitHead. scripts/report-lib.mjs therefore falls back to fixture.source.ref because the payload version now matches this pin. The manifest and shim still name 9cf7fc279c26cf3493b75e703aeadac6d0deb5ee, so reports attribute the new artifact to the previous build. npm provenance identifies 2040d1b71db98e8b2a5d740770c37e17f64316ba as the new build commit. Update crabpot.config.json and crabpot.sourceRef in this shim together, as docs/operations.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 scripts/sync-fixtures.mjs --check
  • node --test test/manifest.test.mjs test/report-provenance.test.mjs
  • npm run report
  • git diff --check

What I checked:

  • Verified introduced change: The pinned diff changes only the package pin, lockfile artifact identity, and declared OpenClaw peer range; main retains 2026.10.1. (plugins/msteams/package.json:7, 0b824fdb5220)
  • Source alignment contract: Operations documentation requires manifest and shim source references to match the published artifact’s build provenance; both MSteams references remain 9cf7fc279c26cf3493b75e703aeadac6d0deb5ee. (docs/operations.md:50, c82f74c2c423)
  • Reachable incorrect report attribution: Report generation uses fixture.source.ref when the artifact lacks gitHead and its version equals the shim pin; this PR makes 2026.10.2 satisfy that comparison while retaining the previous build reference. (scripts/report-lib.mjs:323, c82f74c2c423)
  • Published dependency provenance and policy boundary: The npm artifact and registry metadata omit gitHead and lifecycle scripts; npm provenance identifies build commit 2040d1b71db98e8b2a5d740770c37e17f64316ba. Crabpot materializes and inspects this dependency, establishing the dependency-policy signal; its root and extensions policies were read. (extensions/msteams/package.json, 2040d1b71db9)
  • Prior maintainer fixture decision: fix(fixtures): refresh eight official plugins to 2026.10.1 #461 deliberately updated fallback pins and published-source references together, retaining the frozen host and qualifying its compatibility limitations. (plugins/msteams/package.json:15, f0a68ce3d504)
  • Discussion and checks: The full PR body and comments contain no additional owner decision; the exact-head isolated MSteams check and fixture-lock security check passed, while other checks remained in progress. (0b824fdb5220)

Likely related people:

  • Vincent Koc: Raw commit f0a68ce adds plugins/msteams/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/msteams/package.json)
  • Peter Steinberger: Raw commit 61be4f5 adds plugins/msteams/package.json:18 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 61be4f5165d2; files: plugins/msteams/package.json)

Labels

Label changes:

  • add P2: The dependency refresh introduces incorrect compatibility-report source attribution with a narrow repair.
  • add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool 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:

  • P2: The dependency refresh introduces incorrect compatibility-report source attribution with a narrow repair.
  • rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool 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:23 AM ET / 09:23 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/msteams/openclaw/msteams-2026.10.2 branch October 15, 2026 16:34
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 P2 Normal priority bug or improvement with limited blast radius. 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