Repo tweaks after the switch to uv

[davep]

Followup to #123 that tweaks a handful of things and updates the ChangeLog.

TODO: #123 kills my ability to publish new versions of Hike at the moment. I need to work out what's the uv approach to publishing to test PyPI or real PyPI as a choice.

[davep]

Ugh. Great. So we're having to switch to a tool that adds friction? astral-sh/uv#10878 :-/

[hugovk]

Hmm.

I've only ever used twine to upload from local so don't have experience with Rye or uv's process.

But I've fully switched over to using Trusted Publishing to upload from CI. I find this much easier, you can do it from a tag or GitHub Release, and it's more secure as there's no need for long-lived tokens on my machine.

I realise this is more yak shaving you may not have time for right now, but I'm happy to help out, now or in the future :)

As suggested in #123, in the short term you could keep Rye for publishing and uv for the other stuff.

[davep]

Yeah, before using rye for this I used twine for the longest time. As for the other stuff it's on my long-term todo list to look into, but honestly it's another one of those ever-changing Python ecosystem things that's a struggle to keep up with and which I'm reluctant to depend on given the long history of the ever-shifting packaging landscape (and there's the worry that it seems, from my basic understanding, one that comes with some lock-in to various forges). But I guess that's a blog post I should dump out one day, or something. ;-)

[davep]

I've reverted #123 for now. I like the idea and want to keep on top of things, but just don't have the time or the bandwidth to learn a bunch new stuff right at this moment. Perhaps if/when the tooling settles down and becomes trustworthy.

[hugovk]

Sure thing, and feel free to ping me whenever.

[davep]

Thanks; will do!