openclaw - ✅(Solved) Fix [Bug]: Changelog lists 2026.4.26 released, but npm stable install target is missing [1 pull requests, 2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#73089Fetched 2026-04-28 06:27:40
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
0
Author
Timeline (top)
commented ×2labeled ×2closed ×1cross-referenced ×1

The changelog shows 2026.4.26 under released versions, but npm currently reports:

Latest dist-tag: 2026.4.25. Available versions include 2026.4.26-beta.1 but not stable 2026.4.26

Repro: npm view openclaw dist-tags --json npm view openclaw versions --json openclaw update --tag 2026.4.26 --yes

Observed: update fails with npm notarget because 2026.4.26 stable does not exist in npm registry.

Expected: If changelog marks 2026.4.26 released, npm stable artifact should be available, or docs/changelog should clearly indicate delayed/rolled-back publish.

Root Cause

Observed: update fails with npm notarget because 2026.4.26 stable does not exist in npm registry.

PR fix notes

PR #73259: docs: mark 2026.4.26 as delayed in changelog (#73089)

Description (problem / solution / changelog)

Fixes #73089.

The changelog listed 2026.4.26 as released, but the npm stable install target is missing. This PR updates the changelog headings to reflect the delayed status.

  • Changed ## 2026.4.26 to ## 2026.4.26 (Delayed — not yet published to npm stable) in CHANGELOG.md
  • Changed ## 2026.4.26 - 2026-04-26 to ## 2026.4.26 - 2026-04-26 (Delayed) in apps/ios/CHANGELOG.md

Changed files

  • CHANGELOG.md (modified, +1/-1)
  • apps/ios/CHANGELOG.md (modified, +1/-1)
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

The changelog shows 2026.4.26 under released versions, but npm currently reports:

Latest dist-tag: 2026.4.25. Available versions include 2026.4.26-beta.1 but not stable 2026.4.26

Repro: npm view openclaw dist-tags --json npm view openclaw versions --json openclaw update --tag 2026.4.26 --yes

Observed: update fails with npm notarget because 2026.4.26 stable does not exist in npm registry.

Expected: If changelog marks 2026.4.26 released, npm stable artifact should be available, or docs/changelog should clearly indicate delayed/rolled-back publish.

Steps to reproduce

npm view openclaw dist-tags --json npm view openclaw versions --json openclaw update --tag 2026.4.26 --yes

Expected behavior

If changelog marks 2026.4.26 released, npm stable artifact should be available, or docs/changelog should clearly indicate delayed/rolled-back publish.

Actual behavior

update fails with npm notarget because 2026.4.26 stable does not exist in npm registry.

OpenClaw version

<version 2026.4.26>

Operating system

Ubuntu 24.04

Install method

openclaw update

Model

GPT-5.3-Codex

Provider / routing chain

openclaw update --tag 2026.4.26 --yes -> npm

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

Last known good: v2026.4.21

extent analysis

TL;DR

The issue can be resolved by updating the changelog to reflect the correct version availability or by publishing the stable 2026.4.26 version to the npm registry.

Guidance

  • Verify the version availability in the npm registry using npm view openclaw versions --json to confirm the absence of the stable 2026.4.26 version.
  • Check the changelog documentation to ensure it accurately reflects the release status of version 2026.4.26.
  • Consider publishing the stable 2026.4.26 version to the npm registry if it is indeed ready for release.
  • If the version is not ready for release, update the changelog to indicate the delayed or rolled-back publish status.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The issue seems to be related to a discrepancy between the changelog and the actual version availability in the npm registry. Resolving this issue requires ensuring that the changelog accurately reflects the release status of version 2026.4.26.

Recommendation

Apply workaround: Update the changelog to reflect the correct version availability or publish the stable 2026.4.26 version to the npm registry, as this will resolve the discrepancy and allow users to access the correct version.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

If changelog marks 2026.4.26 released, npm stable artifact should be available, or docs/changelog should clearly indicate delayed/rolled-back publish.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING