[xiangfu0]

Summary

The committed Gemfile.lock pinned the local path gem pinot-client at 1.29.0, stale from the 1.44.0 version bump (commit ce7e4c4). lib/pinot/version.rb and pinot.gemspec declare 1.44.0, so the lockfile's path-gem version was out of sync with the gemspec.

Why it matters

Plain bundle install (what CI uses) silently rewrites the lockfile to 1.44.0, masking the drift. But a frozen/deployment install surfaces it:

$ BUNDLE_FROZEN=true bundle install
The gemspecs for path gems changed, but the lockfile can't be updated
because frozen mode is set
# exit 16

Regenerating the lockfile brings it into agreement with the gemspec.

Change

One line only — the path gem version pin:

-    pinot-client (1.29.0)
+    pinot-client (1.44.0)

No other dependency pins move. This is pure lockfile metadata; no runtime behavior changes.

Validation (local, source @ this branch head)

• BUNDLE_FROZEN=true bundle install → exit 0 (was exit 16 before)
• RuboCop (bundle exec rubocop lib/ spec/) → PASS
• Unit tests (COVERAGE_MIN=95 bundle exec rspec spec/pinot/) → 524 examples, 0 failures, 1 pending; coverage 99.72% (≥95%)
• bundle exec bundle-audit check → no vulnerabilities
• Integration tests against live apachepinot/pinot:1.5.0 QuickStart BATCH (spec/integration/) → 16 examples, 0 failures (unaffected by this metadata change; run on identical source)

Note: Ruby 3.3 lane not exercised locally (only 3.2 target config / 3.4 runtime available in this environment); covered by CI.

[intentlab-ai]

Code Health Review

⏭️ Skipped — This change does not affect analyzed code.

_{Reviewed f5712f3}

[intentlab-ai]

Code Review

✅ Passed

_{Reviewed f5712f3}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.72%. Comparing base (dd6a412) to head (f5712f3).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #67   +/-   ##
=======================================
  Coverage   99.72%   99.72%           
=======================================
  Files          27       27           
  Lines        1103     1103           
=======================================
  Hits         1100     1100           
  Misses          3        3           

Flag	Coverage Δ
unit	99.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[intentlab-ai]

PR Readiness Review

✅ Passed

_{Reviewed f5712f3}

[xiangfu0]

Superseded by #68, which fixes the root cause of this drift rather than the symptom. As noted when this PR was held as draft, auto-release-minor.yml runs bin/bump-version on every push to main, and that script only edited version.rb — so the next auto-release would recreate the pinot-client PATH-pin mismatch this one-line patch fixes.

#68 teaches bin/bump-version to sync the Gemfile.lock PATH pin (and stages it in the release commit), and includes the same current-drift fix (1.29.0 → 1.44.0). Recommend closing this PR in favor of #68 once #68 is reviewed/merged.

[xiangfu0]

Superseded by #68, which landed the durable fix for the recurring Gemfile.lock PATH-pin drift (repairs bin/bump-version plus both auto/manual release workflows, with the lockfile repair this PR made one line at a time). Closing in favor of #68 (merged as e35b636). The #67 branch's one-line edit fixed the symptom once but the next release would have recreated the drift.