npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/Cargo.toml, branch v1.4.5Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.4.52024-08-30T13:09:48+00:00chore: bump to v1.4.52024-08-30T13:09:48+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-30T13:09:48+00:00urn:sha1:36763dc0d821425e088adefd16dc7c4bf3b30f3b
changelog:
* when clone url is ssh use auth for `list` and `fetch` as
they are required
* when clone url is ssh, fallback to https so read events dont always
require auth
* stop asking for git server credentials when pushing `pr/` branch
* fix `no repo events at specified coordinates` error via rust-nostr
v0.34.1 upgrade
chore: bump rust-nostr to v0.34.12024-08-28T21:27:19+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-28T21:27:19+00:00urn:sha1:23c5aadae9b4dc53f00e58f9b0728048c45843a8
this fixed an efficency thing which meant we needed to increase
a timeout during the update which is reverted int his commit. see:
nostr:nevent1qvzqqqqx25pzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyqg5lfwhruw4qjpnlzq0tct0swnuj9dvavz8gsq8npuyygznstw36882alm
chore: bump rust-nostr to v0.34.02024-08-28T15:42:53+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-28T13:20:34+00:00urn:sha1:a5216602749bff55c2773acce098c91942cd3920
bump all rust-nostr packages
I'm not sure I'm completely happy with allowing mutable_key_type
but it is just run inside tests
it appears that Event didn't have the Copy trait in v0.33.0 so I'm
not sure why this warning suddenly appeared
the timeout of client.get_events_of needed to be doubled which could
indicate that an ineffiency has been introduced in v0.34.0
the primary motivation for upgrading now was to get this fix:
nostr:nevent1qqsffl2ld678pjj77rh9k2g4edljmxdu6ew4lvgnglxv7jhu3ru8vvcpp4mhxue69uhkummn9ekx7mqzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6rm2ucm
as I suspect it is also effecting other repositories
eg nostr-profile-manager
chore: bump to v1.4.42024-08-27T18:44:31+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-27T18:44:31+00:00urn:sha1:76a88f81af435a5c11fa7baf1689c82880fdcd5c
changelog:
* include git plugin in release zip
chore: bump to v1.4.32024-08-27T10:59:12+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-27T10:59:12+00:00urn:sha1:190b2f622f44c49aa77f8089d9ca9218c0aade81
changelog:
* fix clone using nostr url
chore: bump to v1.4.22024-08-20T11:33:51+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-20T11:33:51+00:00urn:sha1:daaaa3a21277351638eda04739ac3d7b3716f955
changelog:
* fix only maintainers can push normal branches / tags
chore: bump to v1.4.12024-08-20T11:00:22+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-20T11:00:22+00:00urn:sha1:09ead86c82f773778b984b5bbbd9798155265cd3
changelog:
* fix pushing tags in git-remote-nostr
build: removed git category2024-08-20T10:14:23+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-20T10:14:23+00:00urn:sha1:4c109e0857becca4a5d90568b7c50064436e94cb
as publishing to crates.io now gives error:
`
The following category slugs are not currently supported on crates.io: git
`
chore: bump to v1.4.02024-08-20T09:45:50+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-20T09:45:50+00:00urn:sha1:a3073105ae20747fbf76b70cf0ac4ed5c0a9b1b3
changelog:
* add git-remote-nostr binary
bump nostr-database to v0.33.12024-08-02T12:02:47+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-02T12:02:47+00:00urn:sha1:098bb88b4f313d9a0b32808b42f4b4c17e1771a2
to get latest fixes applied