Skip to main content
Glama

magento.watch

find_upstream_fix

Community fixes merged into magento/magento2 after a release line was cut, with per-version applicability from git apply checks; not Adobe Quality Patches, for those use find_patch. With only distribution and version it lists, newest first, every upstream fix whose code applies cleanly to that version and that the version does not contain yet. Add query (symptoms, error text, feature words or an id like magento2-40867), modules or categories (QPT category names like "GraphQL", "Catalog/Product") to get a ranked list with a 0-100 relevance score and the signals that matched. fixedIn filters by the first release that contains the fix (null for fixes not in any release yet). Mage-OS always returns status "unknown"; a version outside the checked release tags returns status "unknown-version".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRanked mode only, default 10
queryNoFree text: symptoms, error message, feature names, or an upstream fix id
fixedInNoOnly fixes first released in this version, e.g. "2.4.9"; null for fixes not in any release yet
modulesNoModule names with or without the magento/module- prefix
versionYesExact Magento version, e.g. "2.4.8-p3"
categoriesNoQPT category names
distributionYes
includeExcludedNoAlso return entries excluded as features, refactors or test-only changes; each hit keeps its excluded reason

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources