Make Bindings README § Stability static #1948

Activity

1. benalleng commented on Oct 5, 2026

   

   benalleng

   on Oct 5, 2026

   Collaborator

   More actions

   same in https://github.com/payjoin/rust-payjoin/blob/master/payjoin-ffi/javascript/RELEASING.md and https://github.com/payjoin/rust-payjoin/blob/master/payjoin-ffi/python/RELEASING.md see the diff in https://github.com/payjoin/rust-payjoin/pull/1935/changes#diff-725f75d5c3e2b781c3eb21721d2a51f1b2c13ae90b877dedcb2073dab825df7f
2. DanGould

   changed the title [-]Make C# Readme § Stability static[/-] [+]Make ~C#~ Bindings README § Stability static[/+] on Oct 5, 2026
3. DanGould

   changed the title [-]Make ~C#~ Bindings README § Stability static[/-] [+]Make Bindings README § Stability static[/+] on Oct 5, 2026
4. Christopherdominic commented on Oct 19, 2026

   

   Christopherdominic

   on Oct 19, 2026 – with ChatGPT Codex Connector

   Contributor

   More actions

   @DanGould @benalleng I'd like to help with this, but checked current master before proposing a patch: payjoin-ffi/README.md no longer has the version-specific Stability section, and the shared payjoin-ffi/RELEASING.md describes the package version relationship without hardcoded release numbers.

   My intended scope would be to check the JavaScript and Python release guides mentioned above, together with the shared bindings README/release guide, and replace any remaining release-specific examples with consistent <version> placeholders or a link to the shared instructions. I'd preserve commands that need concrete syntax and check the rendered Markdown and relative links, then run the repository's formatting/spelling checks.

   Has the recent bindings release work already satisfied this issue, or is there a remaining example you want covered? I'd appreciate confirmation of the remaining scope before starting a PR.

   AI disclosure: This comment was drafted with OpenAI Codex assistance.