Fixed some stuff to make it more professional looking

Author: ladderlogix

.github/workflows/main.yml

@@ -137,3 +137,62 @@ jobs:
           dnp3time-windows-x86_64.exe/dnp3time-windows-x86_64.exe.sha256
           dnp3time-linux-x86_64/dnp3time-linux-x86_64
           dnp3time-linux-x86_64/dnp3time-linux-x86_64.sha256
+
+  crates_io_publish:
+    name: Publish (crates.io)
+    needs:
+      - create-release
+
+    runs-on: ubuntu-latest
+    timeout-minutes: 25
+    steps:
+      - uses: actions/checkout@v4
+      - uses: dtolnay/rust-toolchain@stable
+
+      - name: cargo-release cache restore
+        id: cargo_release_cache_restore
+        uses: actions/cache/restore@v4
+        with:
+          path: ~/.cargo/bin/cargo-release
+          key: ${{ runner.os }}-cargo-release
+
+      - run: cargo install cargo-release
+        if: steps.cargo_release_cache_restore.outputs.cache-hit != 'true'
+
+      - name: cargo-release cache save
+        id: cargo_release_cache_save
+        uses: actions/cache/save@v4
+        if: always() && steps.cargo_release_cache_restore.outputs.cache-hit != 'true'
+        with:
+          path: ~/.cargo/bin/cargo-release
+          key: ${{ runner.os }}-cargo-release
+
+      - name: cargo login
+        run: |-
+          echo "${{ secrets.CRATES_IO_API_TOKEN }}" | cargo login
+
+      # allow-branch HEAD is because GitHub actions switches
+      # to the tag while building, which is a detached head
+
+      # Publishing is currently messy, because:
+      #
+      # * `peace_rt_model_core` exports `NativeError` or `WebError` depending on the target.
+      # * `peace_rt_model_web` fails to build when publishing the workspace for a native target.
+      # * `peace_rt_model_web` still needs its dependencies to be published before it can be
+      #    published.
+      # * `peace_rt_model_hack` needs `peace_rt_model_web` to be published before it can be
+      #    published.
+      #
+      # We *could* pass through `--no-verify` so `cargo` doesn't build the crate before publishing,
+      # which is reasonable, since this job only runs after the Linux, Windows, and WASM builds
+      # have passed.
+      - name: "cargo release publish"
+        run: |-
+          cargo release \
+            publish \
+            --workspace \
+            --all-features \
+            --allow-branch HEAD \
+            --no-confirm \
+            --no-verify \
+            --execute

CONTRIBUTING.md

@@ -0,0 +1,64 @@
+# Contributing to `dnp3time`
+
+We welcome contributions to the `dnp3time` project! Whether it's bug fixes, features, documentation improvements, or other enhancements, your help is appreciated.
+
+## Getting Started
+
+1. **Fork the Repository**  
+   To start, fork the repository and clone it locally:
+   ```bash
+   git clone https://github.com/<your-username>/DNP3TimmingAttack.git
+   cd DNP3TimmingAttack
+   ```
+
+2. **Set Up Your Development Environment**  
+   You need to have the Rust toolchain installed. If it's not already installed, you can do so with:
+   ```bash
+   curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
+   rustup update
+   ```
+
+3. **Run Tests**  
+   Confirm the project is working correctly by building and running the provided tests:
+   ```bash
+   cargo test
+   ```
+
+4. **Make Changes**  
+   Edit the code, tests, or documentation to improve the project. Be sure to follow best practices and make your changes as clean and modular as possible.
+
+5. **Submit a Pull Request**  
+   After completing and testing your changes:
+   - Push your branch to your fork.
+   - Create a pull request in the [main repository](https://github.com/ladderlogix/DNP3TimmingAttack).
+
+## Code Style
+`dnp3time` follows the Rust 2024 edition and the Rust style guide. Use `cargo fmt` to ensure your code is properly formatted:
+```bash
+cargo fmt
+```
+
+To ensure your code is free of common errors, also run:
+```bash
+cargo clippy
+```
+
+## Reporting Issues
+If you find a bug, file an issue on the [GitHub Issues page](https://github.com/ladderlogix/DNP3TimmingAttack/issues). Please include:
+- Steps to reproduce the issue.
+- Expected vs actual behavior.
+- Relevant output logs (if applicable).
+- Your environment (OS, Rust version, etc.).
+
+## Testing Contributions
+If you add a feature or fix a bug, include tests to verify your changes. Write unit tests wherever applicable and ensure the entire test suite passes:
+```bash
+cargo test
+```
+
+## Feature Requests
+We welcome ideas for improvements! If you have a feature in mind, file a feature request in the [GitHub Issues page](https://github.com/ladderlogix/DNP3TimmingAttack/issues).
+
+---
+
+Thank you for your interest in contributing!

Cargo.lock

@@ -1,15 +1,19 @@
 [package]
 name = "dnp3time"
-version = "0.1.0"
-edition = "2021"
+version = "1.1.0"
+edition = "2024"
+description = """
+Allows you to set the system time using DNP3 time synchronization.
+"""
+authors = ["Stephen Glombicki <[email protected]>"]
+readme = "README.md"
+repository = "https://github.com/ladderlogix/DNP3TimmingAttack.git"
+license = "AGPL-3.0-only"
+keywords = ["dnp3"]
 
 [dependencies]
 tokio = { version = "1.0", features = ["full"] }
 dnp3 = "1.6.0"
 anyhow = "1.0.98"
-windows = { version = "0.48.0", features = [
-    "Win32_Foundation",
-    "Win32_System_SystemInformation"
-] }
 chrono = { version = "0.4", features = ["clock"] }
 clap = { version = "4.5.40", features = ["derive"] }