Skip to content

Conversation

@yyforyongyu
Copy link
Member

@yyforyongyu yyforyongyu commented Nov 4, 2025

Open this PR to track rebase conflicts on the side branch 0-21-staging, which prepares for release 0.21.
Included PRs,

Total commits: 29

@yyforyongyu yyforyongyu added this to the v0.21.0 milestone Nov 4, 2025
@yyforyongyu yyforyongyu added this to v0.21 Nov 4, 2025
@yyforyongyu yyforyongyu force-pushed the 0-21-0-staging branch 2 times, most recently from 86fd4b7 to 57eb251 Compare November 4, 2025 11:50
@yyforyongyu yyforyongyu marked this pull request as ready for review November 4, 2025 18:01
@yyforyongyu yyforyongyu changed the title [draft]: Prepare release 0.21 Merge branch 0-21-staging Nov 7, 2025
ziggie1984 and others added 20 commits November 12, 2025 22:54
The config file format changed. The tool golangci-lint migrate
was used to migrate the old config. However old comments and also
the structure of the disabled linters was preserved.

Moreover the new v2 version introduced new linters, we disable
3 of them because they are very noise and we do not really want
to check for them: funcorder, noinlineerr, embeddedstructfieldcheck.
The custom file is only needed in the tools directory.
And ensure that both versions 1 and 2 implement it.
Define a GossipVersion enum along with a GossipMessage interface to be
satisfied by all gossip related messages. This will be useful later on
when we want to make decisions based on the protocol version that a
message is part of.
Since the gossip protocols are completely disjoint, we need to treat
messages on the two protocols completely separately and should not let
rejections on one protocol affect how we treat messages on the other.
We now make sure we only set the custom channel data in the
lnrpc.Route only if it contains relevant data.
We now return an error when blinded and non blinded attempts are
combined. This was theoretically possible to register a legacy
attempt in combination with a blinded payment. This would have
been prevented by other checks in the code because legacy payments
are not split into shards.
This message type is a message that carries an onion-encrypted payload
used for BOLT12 messages.
This commit creates the necessary endpoints for onion messages.
Specifically, it adds the following:

- `SendOnionMessage` endpoint to send onion messages.
- `SubscribeOnionMessages` endpoint to subscribe to incoming onion
  messages.

It uses the `msgmux` package to handle the onion messages.
The only way to unblock SendCustomMessage is if the peer activates,
disconnects or the server shuts down. This means that if the context is
cancelled, we will still wait until one of those other events happen.

With this commit we thread the context through to SendCustomMessage, so
that if the context is cancelled, we can return early. This improves the
cancellation semantics.
Simplify the struct by removing un-used methods and outdated comments.
Remove the 2 sources of truth here. If we have a signature for the
node, then we have the announcement.
Add a version field to models.Node and a V1 constructor for it.
Remove various unused fields and methods.
This tests was a temporary helper to let devs test the graph SQL
migration before it was plugged in to LND. But that migration has now
shipped and so we can remove this.
Copy over all the code that the graph SQL migration needs to a
separate folder. This will let us advance the main graph SQL CRUD code
without worrying about changing the sql migration code. It will also let
us change the SQL queries without changing the migration. In this
commit, only the migration logic is "frozen" but in an upcoming commit,
the sqlc queries & models will be frozen too.
Copy link
Member

@Roasbeef Roasbeef left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🧇

@Roasbeef Roasbeef merged commit af6816b into master Nov 13, 2025
37 of 39 checks passed
@github-project-automation github-project-automation bot moved this to Done in v0.21 Nov 13, 2025
@yyforyongyu yyforyongyu deleted the 0-21-0-staging branch November 13, 2025 09:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

6 participants