prepare 1.7.0-RC1

[jadamcrain]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @jadamcrain, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is a comprehensive update to transition the project to its 1.7.0-RC1 release candidate phase. It involves synchronizing version numbers across the entire codebase, updating a substantial number of Rust dependencies to ensure stability and leverage new capabilities, and documenting the new features and improvements in the changelog. The changes reflect a significant step towards the next stable release, incorporating new functionalities and maintaining a robust dependency ecosystem.

Highlights

• Release Preparation: This pull request prepares the project for the 1.7.0-RC1 release by updating version numbers across various configuration files and dependencies.
• Dependency Updates: Numerous Rust dependencies in Cargo.lock have been updated to their latest versions, ensuring the project benefits from the most recent fixes and features. Several old dependencies were also removed.
• Changelog Updates: The CHANGELOG.md has been updated to reflect the new 1.7.0-RC1 version and includes several new features and improvements, such as an enhanced outstation ConnectionManager, DirectWriteAbsTime sync, zero-length octet string support, AWS libcrypto TLS backend, and public constructors for Java bindings and mockability.
• Version String Consistency: All relevant project files, including Cargo.toml files, pom.xml files, CMakeLists.txt, and sitedata.json, have had their version strings updated from 1.7.0-M1 or 1.7.0-M2 to 1.7.0-RC1.
• Tokio-Serial Pinning: The tokio-serial dependency has been specifically pinned to version 5.4.5 in dnp3/Cargo.toml, with a note indicating this is due to the library's inconsistent release practices.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request prepares for the 1.7.0-RC1 release by updating version numbers across the project, including Cargo.toml files, pom.xml files, and documentation. It also includes a significant update of dependencies in Cargo.lock, which is expected for a release. The CHANGELOG.md has been updated to consolidate changes from previous milestones and add new ones for this release candidate. The changes are consistent and look good, with one minor suggestion for the changelog.

[gemini-code-assist]

The changelog for 1.7.0-M2 included a bug fix: * :bug: Fix Maven Central deployment issues for post-OSSRH era.. It seems to have been omitted from the 1.7.0-RC1 changelog. Was this intentional? If not, it would be good to include it for completeness.

Suggested change

	* :star: Make HeaderInfo constructor public for mockability in tests. See [#404](https://github.com/stepfunc/dnp3/pull/404).
	* :star: Make HeaderInfo constructor public for mockability in tests. See [#404](https://github.com/stepfunc/dnp3/pull/404).
	* :bug: Fix Maven Central deployment issues for post-OSSRH era.