Request: Git tags and CHANGELOG updates for versions 5.4.3-5.4.5

[jadamcrain]

@berkowski First, thank you for maintaining tokio-serial - it's a critical dependency for many Rust projects doing serial communication.

This code gets used on embedded linux in production power systems. I'm updating dnp3 from 5.4.3 to 5.4.5 and noticed that recent releases are missing some release metadata that would help downstream maintainers make informed decisions about updates.

Current situation

Versions 5.4.3, 5.4.4, and 5.4.5 have been published to crates.io, but:

• No git tags (tags stop at v5.4.1)
• CHANGELOG.md ends at 5.4.2
• No GitHub releases (not really important with tags and crates.io but there were releases for other versions)

This makes it difficult to:

• Understand what changed between versions
• Evaluate whether updates are safe/beneficial
• Reference specific commits for published versions
• Conduct security audits

Commit mapping (reconstructed)

Through some detective work, I believe the mapping is:

• 5.4.2: c86a22f (Mar 4, 2022)
• 5.4.3: 394d9f8 (Mar 23, 2022)
• 5.4.4: 30b58d8 (Nov 2, 2022)
• 5.4.5: current master (~Apr 2025)

Offer to help

I'd be happy to contribute:

1. PR with reconstructed CHANGELOG entries for 5.4.3-5.4.5 based on commit history
2. Documentation on release process (if that would be helpful)

Would it be useful if you created the git tags retroactively? I know it's unconventional but could
help with traceability.

Thanks for considering this! Happy to help in whatever way would be most useful.

[estokes]

You are welcome to create a PR. I am about ready to go through all the PRs that have rolled in since last year, so you're just in time.