Revert unreleased 0.3.2 version bump

[Project516]

What

Reverts the version bump that landed in #11:

• pubspec.yaml: 0.3.2 back to 0.3.1.
• CHANGELOG.md: the 0.3.2 heading is now Unreleased. The entries under
  it are unchanged, they describe real merged work.
• No other 0.3.2 reference remained in the repo.

No library code changed.

Why

#11 merged and bumped the version and changelog to 0.3.2, but no v0.3.2
tag and no GitHub release were ever cut, as its own "Noticed, not fixed"
section flagged. The latest tag is still v0.3.1. A version number in
pubspec.yaml with no tag behind it is a half-finished release, so it goes
back to the last released state.

The package stays at 0.3.1 for now. The bump happens later, as its own
change, when the maintainer wants getTeamEvents pulled into the consuming
app. A version bump here decides when consumers pick a change up; it should
not be a side effect of merging the feature PR that adds it.

Verify

• dart pub get
• dart analyze: no issues
• dart test: 28/28 passing
• dart format --output=none --set-exit-if-changed .: clean

[coderabbitai]

Warning

Review limit reached

Next included review available in 46 minutes.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 7b8c4463-6645-4e70-ada4-455f7cffb6b4

📥 Commits

Reviewing files that changed from the base of the PR and between a9fcb13 and ac5b4bb.

📒 Files selected for processing (2)

• CHANGELOG.md
• pubspec.yaml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Project516]

Review: independent fallback pass, not CodeRabbit. CodeRabbit is rate limited (gh api repos/Project516/statbotics_client/pulls/12/reviews returns empty, so the green check and the bot's comment are both the rate-limit notice, not a review). Reviewed instead by a separate model given only the PR number and the repo.

No blocking findings. It confirmed 0.3.1 matches both the latest git tag and the latest GitHub release, that the revert is complete and minimal against #11's merge commit, and that nothing else in the repo still says 0.3.2.

Two things it raised, both now settled:

It could not verify whether a consumer pins 0.3.2. Checked: SpectrumStrategy/pubspec.yaml pins ref: v0.3.1, a git tag, and pubspec.lock resolves that tag to a commit. A version change on main cannot reach it. SpectrumPit does not depend on this package at all. Nothing downstream breaks.

## Unreleased is a new convention here. True, every prior version went straight from the work commit to a chore: release X.Y.Z commit with a concrete heading. Keeping it anyway: the entry describes real merged work, and the alternative of dropping it means the change is invisible in the changelog until someone remembers to re-add it at release time. That is precisely the kind of "half-remembered at release time" step worth removing. When the release is cut, the heading becomes the version number.

opus-5 on behalf of Project516