Skip to content

chore: release 0.7.0-rc.77 - #128

Merged
ovitrif merged 2 commits into
mainfrom
release/0.7.0-rc.77
Oct 22, 2026
Merged

ovitrif merged 2 commits into
mainfrom
release/0.7.0-rc.77

Conversation

@ovitrif

@ovitrif ovitrif commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

Refs:

Description

  • Releases 0.7.0-rc.77 with fix: let unannounced channels take full-size payments #120: a node that cannot announce channels accepts incoming payments up to the full channel value instead of 10% of it, for channels opened after the update.
  • Bumps the version in Cargo.toml, Cargo.lock, both gradle.properties, bindings/python/pyproject.toml and Package.swift (tag and the new LDKNodeFFI.xcframework.zip checksum), and adds the changelog line.
  • No API changes: the regenerated bindings are identical.

QA Notes

Release

@ovitrif ovitrif self-assigned this Oct 21, 2026
@ovitrif
ovitrif requested review from a team, ben-kaufman and pwltr and removed request for a team October 21, 2026 16:34

@talosmachina talosmachina left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No findings. Releases 0.7.0-rc.77, which is 0.7.0-rc.76 plus #120 (full-value inbound HTLCs on nodes that cannot announce channels). Reviewed f05161e, full tier (dependency manifests and the Swift binary checksum).

What I checked

Read in full: the 7 changed files at the head; git grep rc.76 at the head finds no version left behind outside the changelog history.
Swift package: the v0.7.0-rc.77 tag peels to f05161e, this PR's head, and the published LDKNodeFFI.xcframework.zip release asset has digest sha256:22f121d7...1b97, the same value Package.swift pins.
Contents: the head's only parent is 9ec3dec, the #120 merge, and #120 touched no bindings/ file and no src/lib.rs, which fits "no API changes".
CI: none runs on this branch.

Merge confidence: 5/5, version strings only and the checksum matches the published asset.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-21T16:46:33.615085Z f05161e PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f05161ed45

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread CHANGELOG.md Outdated
@ovitrif

ovitrif commented Oct 21, 2026

Copy link
Copy Markdown
Collaborator Author

Pushed da2fdce: the rc.77 changelog entry now sits at the top of ## Synonym Fork Additions, per the Codex review. No code or version change; the v0.7.0-rc.77 tag and release stay on f05161e.

@ovitrif
ovitrif merged commit 0527e43 into main Oct 22, 2026
@ovitrif
ovitrif deleted the release/0.7.0-rc.77 branch October 22, 2026 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants