selsta opened pull request #11034: rpc: hide sensitive txs from restricted block templates [release-v0.18...

> monero-project/monero #11034

selsta opened pull request #11033: rpc: hide sensitive txs from restricted block templates

> monero-project/monero #11033

selsta opened pull request #11036: wallet_api: reject offline signing with hardware wallets [release-v0.1...

> monero-project/monero #11036

selsta opened pull request #11035: wallet_api: reject offline signing with hardware wallets

> monero-project/monero #11035

<jpk68:matrix.org> IMO, "needs backport" can be added to the following: 11030, 11029, 11024

<ofrnxmr:xmr.mx> any reason why all 0.19 stuff is going thru the backport pr? can people opt to open prs against 0.18 0.19 and master?

<jpk68:matrix.org> Apparently it would just be too complicated with three open branches, IIUC

<ofrnxmr:xmr.mx> i think its just a courtesy to the submitters?

j-berman opened pull request #11037: p2p: use a bool for send()

> monero-project/monero #11037

<ofrnxmr:xmr.mx> i think its added burden and complication for tob to have to cherry pick every pr that is labeled, and potentially missed labels. i guess having all both (0.19 prs, and labels/backport pr) is also an added burden, since youd have to check which one need to be added to label vs which ones have existing pr

<jpk68:matrix.org> FWIW, I would have no problem opening my own

ofrnxmr: we will only do this until v0.18.5.3 is out

afterwards we will go back to the submitter needs to open 2 PRs

<ofrnxmr:xmr.mx> Okok

g

.merge+ 10840 10845

Added

.merges

10840 10845 10964

.merge+ 10986 10991

Added

jpk68 opened issue #11038: CLI wallet will reject correct passwords after inactivity lock is trig...

> monero-project/monero #11038