MCP servers 2026-09-23 08:47 UTC
garmin_mcp
Committed by Taxuspt. Update Category: Bug Fixes & Stability Improvements. Commit details: fix(nutrition): explain the weight-goal targetDate that blocks every settings update. This update resolves known runtime errors and enhances system reliability.
CommitRaw commit message
fix(nutrition): explain the weight-goal targetDate that blocks every settings update
/nutrition-service/settings/{date} is a full-object PUT, and the
object the GET returns carries targetDate -- the weight goal's target
date, not a nutrition field. Garmin rejects the whole request unless
it is after the day being written, so once a user's weight-goal
target date has passed, every nutrition update fails for today and
every future date, with an error that names neither the field nor the
weight goal.
Detects the condition before the PUT and returns a message naming the
field and both dates. Adds an optional target_date argument for
callers who want to move the goal's target as part of the update, and
reports weight_goal_target_date in the success payload so the caller
can see what it ended up as -- this was described in the original PR
but missing from its diff, added here along with the test coverage.