Update chronicles

[markspanbroek]

• allow for newer version of chronicles
• add nimble lock

[emizzle]

Thanks for the PR Mark! Just curious why you decided not to use a version range? Not blocking, so will approve now 👍

[emizzle]

Out of curiosity, why did you decide to not use a version range?

[markspanbroek]

Apologies for the late reply. I have been working with a large number of nimble dependencies lately, and I ran into quite a few bugs in the nimble algorithm. Both the nimble version that comes with nim 2.2.4 and the latest nimble version didn't handle version ranges very well in some cases. I gave up on the upper bounds, and rely on nimble lock files to not have breakage whenever a dependency updates in an incompatible manner.

[emizzle]

@markspanbroek I can't merge due to the unsigned commits. Would you be able to re-commit using a signature? If not, no worries, I can cherry-pick from your branch, but I don't want to take credit for your work.

[markspanbroek]

@markspanbroek I can't merge due to the unsigned commits. Would you be able to re-commit using a signature? If not, no worries, I can cherry-pick from your branch, but I don't want to take credit for your work.

I updated the branch with signed commits. Thanks for being considerate about taking credit, but I don't think that you need to worry. If I remember correctly then cherry-picking or rebasing will still keep my name as author of the commit. Your name would then appear as the committer.

[emizzle]

Thanks mark 🙏