Skip to content

chore(deps-dev): bump openclaw from 2026.6.8 to 2026.6.9 - #3

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/openclaw-2026.6.9
Open

chore(deps-dev): bump openclaw from 2026.6.8 to 2026.6.9#3
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/openclaw-2026.6.9

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 21, 2026

Copy link
Copy Markdown

Bumps openclaw from 2026.6.8 to 2026.6.9.

Release notes

Sourced from openclaw's releases.

openclaw 2026.6.9

Highlights

Changes

Fixes

Complete contribution record

This audited record covers the complete v2026.6.8..HEAD history: 422 merged PRs. The generation manifest also supplies direct commits as editorial input; the grouped notes above prioritize user impact.

Pull requests

... (truncated)

Commits
  • c645ec4 fix(release): terminate command descendants on signal
  • c04126a test(release): align full validation workflow contract
  • 99f3728 fix(ci): deduplicate release Telegram validation
  • aee871b fix(plugins): restore StepFun ClawHub release
  • b86293f docs(changelog): finalize 2026.6.9 ledger
  • 55ee540 test(release): stabilize validation contracts
  • 4ddd670 docs(changelog): finalize 2026.6.9 ledger
  • 0fafe13 merge: synchronize release branch with latest main
  • 437164c docs(changelog): finalize 2026.6.9 ledger
  • 1988e1a chore(deadcode): remove memory wiki helper shims
  • 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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [openclaw](https://github.com/openclaw/openclaw) from 2026.6.8 to 2026.6.9.
- [Release notes](https://github.com/openclaw/openclaw/releases)
- [Commits](openclaw/openclaw@v2026.6.8...v2026.6.9)

---
updated-dependencies:
- dependency-name: openclaw
  dependency-version: 2026.6.9
  dependency-type: direct:development
...

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 Jun 21, 2026
kleinpanic added a commit that referenced this pull request Jun 21, 2026
config/workstream hunt found 3 state-corruption bugs in the WRITE engine (every setStatus/recordProgress/addDecision
hits these):
- #1 empty frontmatter (---\n\n---): content.replace(fm[1]='') matched the empty string at index 0 and inserted the
  new block BEFORE the opening fence → broken file. Now capture open/inner/close fence groups and replace fm[0]
  (always non-empty); an empty block becomes the key line directly.
- #2 setProgressFields used a byte-0 ^---\n anchor (not the BOM-tolerant one) → a BOM/blank-prefixed STATE silently
  DROPPED the progress payload while stamp() updated the timestamp. Now shares the fence-capturing anchor.
- #3 appendUnderSection: an UNTERMINATED code fence left inFence=true to EOF → swallowed the next real ## section
  (entry appended at file end, wrong section). Now falls back to the first ## heading when the fence never closes. 471 tests.
kleinpanic added a commit that referenced this pull request Jun 21, 2026
… vectors + dead consensus backstop

loop/retrieve/inject hunt:
- BLOCKER #1: defaultSemantic()->loadVectorCache()'s JSON.parse was OUTSIDE retrieve()'s try, so a corrupt/truncated
  vector index.json THREW instead of degrading to lexical+trigram (zero results returned, violating the never-hard-fail
  contract). Now the whole semantic path is wrapped + loadVectorCache guards its parse (returns null). Tested.
- BLOCKER #2: the retrieval CONSENSUS backstop was structurally DEAD for single-doc categories — debug/secure/docs
  have only 1 workflow doc, so CONSENSUS_MIN=2 could never be reached (the 'build is flaky -> debug' DoD case the
  semantic arm exists for). Broadened the doc regexes to match the category's AGENT docs (workflow:debug +
  agent:gsd-debug*) so consensus is reachable. Tested: debug/secure fire from retrieval with no intent keyword.
- #5: instructionFor now emits a STOP notice for terminal actions (was 'Proceed to the halt step' — self-contradicting).
- #3: documented the INTENTIONAL plan-phase agent difference (decide.ts research-fan-out vs autonomous direct-plan)
  — not a bug (a test asserts the ORCH-03 fan-out). 488 tests.
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants