Bumps version to 1.83.2

[skrawcz]

To push out telemetry patch.

Changes

How I tested this

Notes

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future TODOs are captured in comments
• Project documentation has been updated if adding/changing functionality.

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to db12ab1 in 9 seconds

More details

• Looked at 7 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. hamilton/version.py:1

• Draft comment:
  The version number has been updated correctly. However, ensure that the checklist in the PR description is completed before merging to maintain best practices.
• Reason this comment was not posted:
  Confidence changes required: 33%
  The PR is straightforward, updating the version number. However, the checklist in the PR description is not completed, which is a best practice to ensure all necessary steps are followed before merging.

2. hamilton/version.py:1

• Draft comment:
  Consider adding a note in the project documentation under docs/ to reflect this version change.
• Reason this comment was not posted:
  Confidence changes required: 33%
  The PR is a version bump, which is straightforward and doesn't violate any of the specified rules. However, it should be documented in the project documentation under docs/ to keep track of version changes.

Workflow ID: wflow_WRvVrvk530CUpc0U

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.