On 10 July, Hyvä shipped a coordinated release across its core packages: theme-module 1.5.2 and 1.4.10, default-theme 1.5.2 and 1.4.10, and the corresponding CSP variants. While none of these are headline-grabbing major versions, the cumulative effect is a meaningful quality-of-life improvement for every Magento merchant running Hyvä. Here is what changed, why it matters, and what you should do about it.
A dual-track release strategy
One of the first things to notice is that Hyvä continues its dual-track release pattern. Version 1.5.x targets the latest Hyvä stack (aligned with newer Magento/Mage-OS versions and Tailwind v4), while version 1.4.x receives backported fixes for merchants on the previous branch. This is thoughtful maintenance: it means you are not forced to upgrade your entire stack just to get critical bug fixes.
The 1.5.2 release contains the same changes as their 1.4.10 counterparts, plus a few extras specific to the newer branch. This means every Hyvä merchant benefits from this release, regardless of which branch they are on.
Theme module: the fixes that matter
The theme-module updates are focused on stability and compatibility.
Snap-slider updated to v2.2.3. The snap-slider component is used across product carousels, related products, and other horizontal scrolling elements throughout a typical Hyvä storefront. Keeping this dependency current prevents the kind of subtle rendering inconsistencies that can creep in over time.
Mage-OS sample data deployment fixed. The hyva:sampledata:deploy command now works correctly on Mage-OS installations. Previously, an unverifiable package check was treated as "not available," blocking deployment entirely. This is significant for the growing Mage-OS community: it signals Hyvä's continued commitment to compatibility beyond just Adobe Commerce.
Stale DI cache fatal error resolved. When the compiled dependency injection cache was stale, hyvaBaseThemes could compile as null, causing a fatal error. This is the kind of issue that surfaces unpredictably, typically after deployments or cache clears, and can be maddeningly difficult to diagnose. Having it fixed upstream saves real debugging time.
Date format TypeError fixed. The Date::getDateYMD() method was throwing a TypeError for locales that use day-first slash date formats, such as nl_BE and en_GB. For any merchant serving European markets, this was a real pain point. Date formatting errors do not just look bad. They can break form validation and order processing flows.
Default theme: UI polish and design token evolution
The default-theme release is where the user-facing improvements live.
-
The ink design token replaces fg: This is a naming change worth paying attention to. Hyvä is introducing ink as a clearer, more intuitive replacement for the fg (foreground) design token. The old fg token remains as a fallback for now, but the direction is clear: future npm package updates will eventually remove it. If you are building custom Hyvä themes, start adopting ink in your new work now. This is the kind of change that is painless to adopt early and annoying to retrofit later.
-
PDP media fullscreen arrow fix: Product pages with a single image were incorrectly showing left-right navigation arrows in the fullscreen gallery view. Small, but the kind of detail that separates a polished storefront from an unfinished one.
-
Minicart option rendering fixed: Custom product options were not rendering correctly in the minicart. For merchants selling configurable products with options, which is most merchants, this directly impacts the shopping experience at a critical conversion point.
-
Pagination edge case resolved: Clicking "next" on the last pagination page was incorrectly redirecting to the first page instead of staying put. This creates a confusing loop for customers browsing large catalogues.
-
Browser-sync BASE_URL fix (1.4.10 only): The browser-sync.config.cjs rewrite rules were stripping window.BASE_URL down to /, breaking JavaScript that relies on absolute request URLs during local development.
-
Configurable product gallery pager: Improved pager visibility for configurable products ensures that when a customer selects a different variant, the image gallery navigation updates and remains clearly visible.
What this means for your roadmap
If you are running Hyvä, here is the practical takeaway:
-
Update promptly: None of these changes should introduce breaking changes, but they fix real issues that affect production storefronts and developer workflows.
-
Adopt the ink token: Do not wait for fg to be removed. Start using ink in any new theme work. This is a clear signal of where Hyvä's design system is headed.
-
Test your date-dependent features if you serve European locales: The fix should resolve issues automatically, but it is worth verifying that date pickers, order dates, and any custom date formatting work correctly post-update.
-
Check your minicart rendering for configurable products: This fix may resolve customer-facing issues you have been working around.
The bigger picture
What impresses about this release is its attention to the edges. Mage-OS compatibility, European locale support, design system naming clarity: these are not the kind of changes that make headlines, but they are exactly the kind of changes that determine whether a platform is genuinely production-ready across diverse use cases.
Hyvä's dual-track maintenance also deserves recognition. In an ecosystem where "upgrade to get the fix" is too often the only answer, providing backports to the 1.4.x branch shows respect for merchants' real-world upgrade timelines.
About On Tap
On Tap is a growth-focused eCommerce consultancy and Hyvä partner, specialising in high-performance Magento storefronts for mid-market and enterprise merchants. From Hyvä theme updates and design system migration to full platform upgrades and ongoing maintenance, On Tap helps merchants keep their storefronts polished, performant, and production-ready.
If you need help planning your Hyvä update or migration, get in touch.
