chore: add new change log#472
Conversation
📝 WalkthroughSummary by CodeRabbit
WalkthroughAdds a ChangesDevnet logger filter
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
Comment |
|
❌ Missing Changeset Please add a changeset describing your changes: pnpm changesetIf your changes do not need a version bump (docs, CI, refactoring), For dependency updates, use the |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Line 7: Update the changelog entry for the devnet log filter change to include
existing ckb-miner.toml configurations in the opt-in guidance, directing users
to edit the [logger] filter there as well; keep the existing ckb.toml guidance
intact.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 116bfd02-8445-4600-a377-909a9942a8d0
📒 Files selected for processing (2)
.changeset/devnet-log-filter-info.mdCHANGELOG.md
💤 Files with no reviewable changes (1)
- .changeset/devnet-log-filter-info.md
|
|
||
| ### Patch Changes | ||
|
|
||
| - 406415e: Change the default devnet log filter from `warn,ckb-script=debug` to `info,ckb-script=debug` in the `ckb.toml` / `ckb-miner.toml` templates (and the config editor's embedded reference templates). A healthy devnet produces almost no `warn`-level output, which left the `offckb status` Logs panel permanently empty and looked broken; `info` keeps the per-block log stream visible while `ckb-script=debug` still surfaces script execution details. Applies to newly initialized chains — edit `[logger] filter` in your existing devnet `ckb.toml` to opt in. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Include ckb-miner.toml in the existing-config guidance.
This entry says the default changed in both ckb.toml and ckb-miner.toml, but only tells users to edit an existing ckb.toml. Please mention ckb-miner.toml as well, or clarify why it does not require a manual update.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CHANGELOG.md` at line 7, Update the changelog entry for the devnet log filter
change to include existing ckb-miner.toml configurations in the opt-in guidance,
directing users to edit the [logger] filter there as well; keep the existing
ckb.toml guidance intact.
* fix: default devnet log filter to info,ckb-script=debug (#471) A healthy devnet emits almost no warn-level logs, so with the previous default filter (warn,ckb-script=debug) the `offckb status` Logs panel stayed permanently empty and looked broken. Switch the devnet ckb.toml and ckb-miner.toml templates (and the config editor's embedded reference templates) to info,ckb-script=debug so the per-block log stream is visible while script debug output is preserved. Existing chains keep their current filter; edit [logger] filter in the devnet ckb.toml to opt in. Co-authored-by: Claude Fable 5 <noreply@anthropic.com> * chore: add new change log (#472) --------- Co-authored-by: humble-little-bear <retric@ckba.build> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
No description provided.