AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 19 Bitcoin

schemas: remove old deprecations, add missing deprecations/added fields

Public commit record

What the developer wrote

Authored by daywalker90

85/100 · Strong
schemas: remove old deprecations, add missing deprecations/added fields

Also made fields not go optional if they are deprecated in the case that their parent is also deprecated. This makes more sense imo when you deprecate a whole command.

I added deprecation annotation for the .proto file as well so that later in the convert.rs file it properly annotates everything to allow for deprecated stuff.

Also fixed one propagation bug for the added/deprecated fields, that's why there are some additional changes of some fields.

Changelog-None
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
The short version

What changed, and why it matters

This commit is a large, routine cleanup of API metadata in Core Lightning. It marks many old RPC commands and fields as deprecated, removes some long-deprecated fields from generated gRPC/JSON schemas, and fixes version annotations in the code generator. There is no direct evidence of a security vulnerability being patched; the changes are about API lifecycle management and generated bindings.

Recommended action

Treat as a normal maintenance/deprecation commit. Review downstream consumers of the removed or newly-deprecated RPC/gRPC fields to ensure compatibility, but no urgent security action is indicated by the diff itself.

Security signals we found

01

Large generated-code churn with deprecation annotations

02

Removal of deprecated fields from public RPC/gRPC schemas

03

No explicit security fix or vulnerability disclosure in commit message

04

No changes to cryptographic, authorization, or network parsing logic visible in diff

Risk score

Why this scored 19/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 3/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.