Repository navigation
v1.0.14 - #49
v1.0.14#49
Conversation
`sync`, `update` and `reset` each ended their publish loop with one
`GET definitions/re-initialize`. The runtime had reduced that endpoint to a
no-op ("retained for API compatibility") and has now removed it — the moment
the call was made is right, and `POST definitions/publish/completed` takes it
over with real work behind it.
That work matters more than it looks: the runtime's discovery endpoint cache
now carries no TTL, so this call is its only automatic invalidation. A sync
that does not make it leaves that runtime resolving cross-domain calls by
whatever it learned at startup, until its pod restarts.
The response is always HTTP 200 with per-hook outcomes in the body, so
`publishCompleted` reads `success` from there rather than from the status code,
and each hook's outcome is printed. `Refreshed` and `SkippedNotOwner` are
successes, `Disabled` means that runtime has no discovery cache, `Failed` means
nothing else will retry it.
Against a runtime that predates the new endpoint this call 404s and the command
prints the same warning without failing — the previous behaviour, since the old
endpoint's failure was swallowed too.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
feat(api): signal publish-completed instead of the removed re-initialize
Add offline SQL generation for Master schema attribute indexes
◈ PR LensNote This merges
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
No description provided.