<feed xmlns='http://www.w3.org/2005/Atom'>
<title>npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/test_utils/src, branch v1.3-beta1</title>
<subtitle>Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
</subtitle>
<id>https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/atom?h=v1.3-beta1</id>
<link rel='self' href='https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/atom?h=v1.3-beta1'/>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/'/>
<updated>2024-07-02T07:54:55+00:00</updated>
<entry>
<title>feat(send): tag each maintainer's repo event</title>
<updated>2024-07-02T07:54:55+00:00</updated>
<author>
<name>DanConwayDev</name>
<email>DanConwayDev@protonmail.com</email>
</author>
<published>2024-07-02T07:54:55+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/commit/?id=58cc0a9662e1bd087c2910eb15aa7568f088bba5'/>
<id>urn:sha1:58cc0a9662e1bd087c2910eb15aa7568f088bba5</id>
<content type='text'>
instead of just tagging the first maintainer's repo event and each
maintainer with a p tag

This allows for easier discoverability of the proposal when:
 * the first maintainer hasn't issued a repo event
 * the maintainers change over time and the single tagged repo event
   is no listed as a maintainer in anyone elses repo event
</content>
</entry>
<entry>
<title>test: fix test affected by user config</title>
<updated>2024-07-01T05:29:40+00:00</updated>
<author>
<name>sommerfeld</name>
<email>sommerfeld@sommerfeld.dev</email>
</author>
<published>2024-06-28T22:21:29+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/commit/?id=cc1cc62d8bd79920249f0738c20d5546f5363f28'/>
<id>urn:sha1:cc1cc62d8bd79920249f0738c20d5546f5363f28</id>
<content type='text'>
applies:
nostr:note14jnggugkcf9vg42tcu6h8c842xlxacsatw7uf889xjjdtqr0ptlsfa5tyh

closes
nostr:note1mm77j27kvmkwvvvvth7w4atgjhxrydafl5jkhh7eztkx4fxq4nqq6fnd6y
</content>
</entry>
<entry>
<title>feat(login): login with nip46 remote signer</title>
<updated>2024-06-28T14:16:43+00:00</updated>
<author>
<name>DanConwayDev</name>
<email>DanConwayDev@protonmail.com</email>
</author>
<published>2024-06-28T14:16:43+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/commit/?id=a82546b70303000b4fc053a1ee21d3d8c7d6ad66'/>
<id>urn:sha1:a82546b70303000b4fc053a1ee21d3d8c7d6ad66</id>
<content type='text'>
and save details in git config
</content>
</entry>
<entry>
<title>refactor: remove fresh test config</title>
<updated>2024-06-26T06:56:10+00:00</updated>
<author>
<name>DanConwayDev</name>
<email>DanConwayDev@protonmail.com</email>
</author>
<published>2024-06-26T06:56:10+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/commit/?id=6b06e874119ceca1a9dac1b94dcfe6e06aacd7b9'/>
<id>urn:sha1:6b06e874119ceca1a9dac1b94dcfe6e06aacd7b9</id>
<content type='text'>
as config is now stored using git config and cache is conditionally
stored in local ./git folder under test conditions
</content>
</entry>
<entry>
<title>refactor: replace keys with signer</title>
<updated>2024-06-25T08:06:47+00:00</updated>
<author>
<name>DanConwayDev</name>
<email>DanConwayDev@protonmail.com</email>
</author>
<published>2024-06-25T08:06:47+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/commit/?id=b63bfc9a34657c5767c507deb7c059e24dd22779'/>
<id>urn:sha1:b63bfc9a34657c5767c507deb7c059e24dd22779</id>
<content type='text'>
so that nip46 bunker signing can be added
</content>
</entry>
<entry>
<title>feat(login): store in git config and use cache</title>
<updated>2024-06-24T08:39:18+00:00</updated>
<author>
<name>DanConwayDev</name>
<email>DanConwayDev@protonmail.com</email>
</author>
<published>2024-06-24T08:39:18+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/commit/?id=173ab188b326fbe78cfba4ab455a74619f4556bb'/>
<id>urn:sha1:173ab188b326fbe78cfba4ab455a74619f4556bb</id>
<content type='text'>
replace ngit yaml file config with:
 * nsec / ncryptsec / npub in git config in nostr.* namespace
 * sql database cache for metadata and relay events

allow different logins to be used for different git repositories by
storing login in local git config
</content>
</entry>
<entry>
<title>build: fix CLITesterConfirmPrompt succeeds with</title>
<updated>2024-06-21T22:31:34+00:00</updated>
<author>
<name>DanConwayDev</name>
<email>DanConwayDev@protonmail.com</email>
</author>
<published>2024-06-21T21:18:12+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/commit/?id=681fdd7683363c62251ecd8dabcc1931a18f4840'/>
<id>urn:sha1:681fdd7683363c62251ecd8dabcc1931a18f4840</id>
<content type='text'>
when the non-default option correctly sent
</content>
</entry>
<entry>
<title>chore: bump rust-nostr to v0.32.0</title>
<updated>2024-06-13T08:09:00+00:00</updated>
<author>
<name>DanConwayDev</name>
<email>DanConwayDev@protonmail.com</email>
</author>
<published>2024-06-11T15:21:44+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/commit/?id=f1b3fcc40ab666d8def97096d1942c274da9b279'/>
<id>urn:sha1:f1b3fcc40ab666d8def97096d1942c274da9b279</id>
<content type='text'>
both nostr and nostr-sdk packages and also in test_utils

fix the many breaking changes

fix: ignore trailing slash when depuplicate relays for send events.
this was picked up as TagStandard::RelayMetadata has started adding
a traling slash.

refactor cli output test function `expect_send_with_progress` so that
relays can succeed / fail in a random order
</content>
</entry>
<entry>
<title>refactor: bump rust-nostr to v0.30 use ncryptsec</title>
<updated>2024-06-11T11:33:09+00:00</updated>
<author>
<name>DanConwayDev</name>
<email>DanConwayDev@protonmail.com</email>
</author>
<published>2024-04-18T06:39:27+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/commit/?id=7c6a5ab4c5e7a81c7442061029b9230748a6639d'/>
<id>urn:sha1:7c6a5ab4c5e7a81c7442061029b9230748a6639d</id>
<content type='text'>
bump nostr and nostr-sdk packages and also in test_utils

remove custom ncryptsec implementation and use the newly
added implementation nip49 version in rust-nostr

note a patched v0.30 is used so that log_n is exposed so that
user can be warned it might take a few seconds to decrypt.
this has now been merged into the library.

note that this will no longer decrypt existing ncryptsec values as
it is uses a longer string. this should therefore be bundled with
the upcoming change to storing nsec and ncryptsec in git config.
</content>
</entry>
<entry>
<title>feat(send): `in-reply-to` tags npubs and events</title>
<updated>2024-05-07T08:10:33+00:00</updated>
<author>
<name>DanConwayDev</name>
<email>DanConwayDev@protonmail.com</email>
</author>
<published>2024-04-22T06:26:15+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/commit/?id=10498b953d36304b441fcb162155c2487046206f'/>
<id>urn:sha1:10498b953d36304b441fcb162155c2487046206f</id>
<content type='text'>
in addition to being used to create a new proposal revision,
in-reply-to can now be used to reference other events and npubs.

for example an issues or kind 1 threads where the proposal is relevant

the proposal will only be marked as a revision if the first parameter is
a reference to an existing proposal root
</content>
</entry>
</feed>
