npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src, branch v1.5.3Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.5.32024-11-12T11:42:26+00:00fix: send event error message2024-11-12T11:42:26+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-12T09:49:58+00:00urn:sha1:da569eeebe16ff8af78bb16883c5f8e9c4514d18
rust-nostr v35/v36 changed the `pool.send_event_to` error message to
use 'event/s not published' instead of the error message
from the relay. `relay.send_event` supplies the useful error message.
test: prevent signer commentary2024-11-12T11:42:25+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-12T08:28:24+00:00urn:sha1:13c21857da897f710d6381547748d6ab92e813cc
identification of signer has been removed from rust-nostr.
until it is added back in we must always prompt the user about
signing as if its a local signer the message will be removed
before the user sees it.
unfortunately this is picked up by the tests so we must
only prompt the user when not running tests.
fix: get correct nip46 npub in edge case2024-11-12T11:42:24+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-12T08:06:44+00:00urn:sha1:c16bec6ce79b9822497659fe11cf10d8fe905eb7
when there is an npub listed in git config but login was via direct
cli arguments to the current process, the wrong npub would be used.
this is the case for the ngit_init tests.
this can be more eligantly if rust-nostr NostrConnect::new() were
updated to accept user public key as requested here:
https://gitworkshop.dev/r/naddr1qvzqqqrhnypzq6xcz9jerqgqkldy8lpg7lglcyj4g3nwzy2cs6u70wejdaj7csnjqy88wumn8ghj7mn0wvhxcmmv9uqq5un4wd6z6mn0wd68y2z2qh0/issues/note1qa2pty0mnjhsme3thza24u3nv8u7859fqw2qg6fuyx9w00e2gekqvl3yg9
fix(login): only get signer npub when unknown2024-11-11T22:09:53+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-11T17:20:37+00:00urn:sha1:574acb16414bca4b30e77abca64ee180695109c3
on get the user public key from the remote signer when it is unknown
so that read operations aren't blocked by being unable to reach
remote signer
chore: bump rust-nostr v0.362024-11-11T22:09:21+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-11T13:08:35+00:00urn:sha1:694325fa25e281b1a4c9d7f275f1a8e0f1ad7abf
bump all rust-nostr packages to latest issued version.
there have been some breaking changes to nip46 and this applies
these changes.
feat(remote): show help when called directly2024-11-11T22:07:48+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-04T12:29:49+00:00urn:sha1:35ad07180e418931dd499f799d704672d27ff35b
instead of printing an error when `git-remote-nostr` is called
directly instead of via plugin, provide some guidance
fix(init): remove broken blaster2024-11-11T22:06:50+00:00DanConwayDevDanConwayDev@protonmail.com2024-10-31T20:29:59+00:00urn:sha1:e07d8bcf3640f16b91f872817939376c7305891a
muntiny wallet has shut down and removed its blaster relay
fix(init): dont err when nostr remote and no ann2024-10-31T09:33:18+00:00DanConwayDevDanConwayDev@protonmail.com2024-10-31T09:32:38+00:00urn:sha1:a0d147ba1f14468924f291c3bcf51b25329f4204
when the user has set a remote to a nostr url but hasn't initiated
the repository on nostr - dont error but instead use the identifier
in the remote
chore: bump rust-nostr to patch near v0.36.02024-10-28T15:41:14+00:00DanConwayDevDanConwayDev@protonmail.com2024-10-28T15:41:14+00:00urn:sha1:ae87aedae9696f4c855ac3dc47e61faec9d07c15
bump all rust-nostr packages
refactoring code based on breaking changes
upgrading to patched version to address signer issue:
nostr:nevent1qvzqqqqqqypzq6xcz9jerqgqkldy8lpg7lglcyj4g3nwzy2cs6u70wejdaj7csnjqy88wumn8ghj7mn0wvhxcmmv9uqzpsw5ph8le2n2kh6uchftawt74hddazk9tp7wjmz967y2l0uva5rc7hsstq
refactor: replace sqlite with lmdb2024-10-28T15:05:38+00:00DanConwayDevDanConwayDev@protonmail.com2024-10-28T15:05:38+00:00urn:sha1:5979e13cdc65ea78894dbcab3acde11b246889a7
as sqlite is depricated in rust-nostr