Repository navigation
Release v0.55.7: Mercado Libre callback, cron-safe releases, OpenSSL - #1809
Merged
Merged
Conversation
(cherry picked from commit 45c66c5)
…g cron before retiring the old backend
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release v0.55.7: a Mercado Libre callback fix, a release-script fix for the onboarding cron, the OpenSSL image update, and what is on main since v0.55.6 (#1804, #1805).
Changes
connectors/mcp-oauth-callback.controller.ts). Mercado Libre posts its notifications to the OAuth redirect URI that sellers paste as the notification URL. The handler only answers 200 and reads nothing, but the global 100-per-minute limit applied: 1,756 × 429 on 2026-11-19 (1,101 in one minute), and Mercado Libre retries every non-200. The handler is now@SkipThrottle(). The GET redirect keeps the global limit.deploy/cloud/release.sh). The cron is a host systemd service whose one HTTP call runs 3 to 8 minutes. On 2026-11-19 the v0.55.6 release stopped the old backend in the middle of the 11:17 run (HTTP 502 after about 20 mails). Step 5 now waits for the units inCRON_UNITS(defaultanythingmcp-onboarding-cron.service) to finish, up toCRON_WAIT_TIMEOUT(600 s), before it stops the old colour. Hosts without systemd skip the wait. The header comment that still described a GitHub Actions call is corrected.Dockerfile):apk upgrade --no-cachein the runner stage (folds Upgrade Alpine packages in the runtime image for OpenSSL fixes #1808, Trivy alerts Jev by TypeSafe adapter: typed yes/no, classification and scoring with probabilities #757 to ci: render the README banner and the social preview from the catalog #766).Type
Testing
mcp-oauth-callback.controller.spec.tschecks the skip metadata on the POST handler and its absence on the GET redirect (35/35 pass locally,npx jest --maxWorkers=2 src/connectors/mcp-oauth-callback.controller.spec.tsinpackages/backend).eslinton both files: clean.deploy/cloud/release.test.shscenario 1 now runs with a stand-insystemctlthat reports the cron active for two checks, and asserts that the release waited and checked three times. Runs in CI ("Cloud release script (blue/green)").docker run --rm node:26-alpine sh -c 'apk upgrade --no-cache && apk info -v | grep -E "^lib(ssl|crypto)3"'shows 3.5.9-r1 (r0 before).Both deployment modes: the throttle change applies to Cloud and self-hosted alike. The cron wait only exists in the Cloud release script; self-hosted is unaffected.
Checklist
Related Issues
Folds #1808. Relates to #1774.