Skip to content

Mage-OS Shopping Feed 1.0.0

Latest
Latest

Choose a tag to compare

View all tags
@mattmacrocket mattmacrocket released this 09 Sep 20:44
· 1 commit to main since this release
v1.0.0
f14a763

Mage-OS Shopping Feed 1.0.0

All 27 CI checks passed for release commit f14a763, including unit tests, integration tests, coding standards, and dependency-injection compilation across the configured Magento Open Source and Mage-OS platforms. View the passing release run.

The first stable release combines Generic, Google Shopping, Google Local Inventory, and Google Promotions support in the mage-os/module-shopping-feed package. It uses the MageOS_ShoppingFeed module identity and does not replace or migrate the older Rocket Web packages.

Changes

  • Hyva simple-product custom options initialize without RequireJS and update the displayed price. Configurable swatch links include numeric attribute IDs so the advertised child is selected on Hyva, while retaining legacy attribute codes.
  • Request-selected microdata is limited to an enabled child of the current configurable product on the current website. Invalid selections fall back to the parent.
  • Repeated queue lookups remain independent, allowing every due feed to be scheduled even when another feed is already queued.
  • HTML entity decoding cannot introduce a tab or line break that shifts output columns. JSON-looking text settings retain their scalar type when saved and loaded.
  • Simple and grouped product links retain nonstandard ports. Uploads stop when the configured remote directory cannot be entered.
  • Configurable parent-stock inheritance uses Magento salability, so a zero-quantity parent no longer marks available variants out of stock.
  • Empty column defaults are normalized before sanitization, avoiding PHP 8.1+ deprecation notices when saving feeds.

The complete changelog covers the consolidation, isolated identifiers, generation, MSI, Promotions, and security work included in this release. The Hyva fixes are compatibility corrections; testing did not establish a Mage-OS 3.5 regression.

Installation and upgrade

composer require 'mage-os/module-shopping-feed:^1.0'
bin/magento module:enable MageOS_ShoppingFeed
bin/magento setup:upgrade
bin/magento cache:clean

Use the PHP version supported by the selected Mage-OS or Magento Open Source release, within the package's PHP 8.1 through 8.5 constraint. The package requires magento/framework 103.0.6-p15 or later in the 103.x series. Complete the normal production deployment steps for the target project.

For an existing dev-main installation, back up the database and feed configuration, update the Composer constraint to ^1.0, then regenerate and compare a feed before re-enabling schedules or uploads. There is no automatic migration from the Rocket Web packages. JSON-looking scalar settings now have an explicit storage marker; downgrading to older development code requires retaining the corrected decoder or restoring compatible configuration data.

Validation and limits

Local acceptance used Mage-OS 3.5.0, PHP 8.4.24, and Hyva on Magebox. The PHP suite passed 354 tests with 721 assertions; all five frontend checks passed. A complete default-store run processed 148 visible products and exported 160 rows with 29 columns. All exported prices and stock values matched the storefront data. All 663 unique product and image URLs returned HTTP 200, and all 38 available configurable variants selected correctly with matching prices and no browser errors. Five image-less gift-card products were excluded by the configured required-image filter.

The validation record describes the checks and evidence. GitHub Actions separately covers the configured Magento Open Source matrix and Mage-OS 3.4.0. The current CI run history is the authority for CI status.

Local file validation does not establish Merchant Center approval, a live FTP/SFTP transfer, production-scale performance, or Google Ads delivery on Hyva. Merchant-specific catalog data, account settings, transfer destinations, and customized themes still need acceptance in the target environment. The existing Google Ads event bridge uses RequireJS and is not a Hyva integration.

Documentation: GitHub Wiki. Security reports: private reporting policy.

For setup and troubleshooting, use the Shopping Feed support bot on Rocket Web. Select Open support chat on the product page.

Assets 2
Loading