Fix: Filter Gradle Release Notes from Deprecation Check

[shining-cat]

Fix False Positive in Deprecation Check

Summary

Issue #11 was a false positive. The deprecation check workflow caught Gradle 9.6.1's release notes banner, not an actual deprecation warning in our code.

Root Cause

What happened:

• Workflow runs: grep -i "deprecat" build-output.log
• Gradle 9.6.1 welcome banner includes:

  Here are the highlights of this release:
   - Improved Configuration Cache hit rates
   - Additional CLI rendering options
   - Important project hierarchy lookup deprecations
  

• The grep caught line 3 of that banner
• Workflow reported it as a deprecation warning

Why SimpleHIIT didn't hit this:

• SimpleHIIT uses Gradle 9.5.0
• The 9.6.1 banner text is new
• SimpleHIIT's deprecation check passed cleanly

Solution

Added regex filter to exclude Gradle release notes bullet points:

grep -E -v '^ - .*(deprecat|Deprecat)'

This preserves real deprecation warnings while filtering banner text.

Testing

✅ Tested locally against the September 1st artifact
✅ Filter now produces zero matches (was 1 false positive)
✅ Pattern won't filter actual deprecation warnings (those don't start with -)

Verification

After merge, the next monthly sanity check will:

• Still catch real deprecations
• No longer create false-positive issues from Gradle banners

Closes

Closes #11