Repository navigation
Release javascript-modules-engine 1.3.1 #674
Description
✅ Summary
Minimum Jahia version
We aim at reducing the possible deployment matrices by regularly bumping up the minimum Jahia version when releasing new versions of our modules. When creating a Release ticket for a module, consult with your PM to identify the new minimum Jahia version this module must be associated with. The default guideline is for a new module release to be compatible with the 2 previous releases.
Current Jahia Version: 8.2.1.0
Desired Jahia Version: 8.2.1.0 (no change, kept on purpose)
📜 Testing matrix
Notes for release testing:
Minor release: new image API (<JImage> / getImageProps), cache dependencies collected automatically by buildNodeUrl, absolute URL option, children in client-only islands, plus fixes:
#789 #783 #810 #786 #811 #807 #788 #792 #680 #681 #715 #813 #790 #668 #793
Without a DAM or an image resizer, JImage serves the original file for every candidate: check srcset/sizes/alt, not the resizing. The build now uses Vite 8 / Rolldown (#668), and Vite 6 to 8 stay supported.
Version matrix
We aim at clearly documenting the possible deployment scenarios in a matrix and specify which ones are expected to be tested or not. In the testing matrix, always use the latest patch version of a particular release
The following combinations should be validated:
- minimum Jahia version (according to the pom.xml)
- Jahia 8.2.1.x
ℹ️ If you are releasing for the main branch of a module, make sure to complete the checklist below when working on the ticket.
✏️ Prepare checklist
- All other tickets within that milestone are are closed
- Testing matrix and Minimum Jahia version are detailed
- Jahia-parent (minimum Jahia version) was updated if requested in the ticket
- Release creation has been triggered from the Github Release UI (detailed documentation) — 1.3.0 was released to staging (run) then abandoned, version burned. 1.3.1: release run
🚦 Tests checklist
General
- Manual tests detailing testing steps for validating the release of this module are present on Testrail
- Automated tests using the release artifacts were executed against the oldest and newest release of Jahia
Module migration
- Upgrade from the previous released version of the module was tested
- The upgrade did not require clearing the browser cache (i.e. missing labels)
While Testing
- No warnings or errors are present in the browser console when testing the module
- No warnings or errors are present in Jahia logs when testing the module (incl. migration)
- Select a random set of fixes from the release and verify them on the minimum jahia-version
After Testing
- Tested combinations (Jahia versions, modules versions) are listed in this released ticket
-
Tested scenarios not detailed in Testrail are listed in this release ticket -
The version was updated in the Selenium integration tests
🚀 Publication checklist
- The release changelog was prepared — draft release
- In case of a major release, a Breaking Changes section is present in the Changelog
- The artifact was released on Nexus
- If the module is included in Jahia distribution, jahia-pack-private was updated with the released version — main: https://github.com/Jahia/jahia-pack-private/pull/1213
-
⚠️ If the module has a dependency to a recent release of graphql-dxm-provider, server-availability-manager or personal-api-tokens, contact the Cloud team to require their approval before publication. - If applicable, corresponding academy pages were published
- The module was published on the store
- The modules releases log page on the Academy was updated
- A message was published on slack #releases channel
- The milestone on GitHub was closed
Activity
Fgerthoffert commentedon Oct 14, 2026
✅ 1.3.1 released to staging: tag
1_3_1frommain, release run fully green (Maven + npm + SBOM)📦 Nexus staging:
jahia_staging_releases-3114, https://devtools.jahia.com/nexus/content/repositories/jahia_staging_releases-3114/org/jahia/modules/javascript-modules-engine/1.3.1/ (Nexus login required)📦 npm:
@jahia/create-module,@jahia/javascript-modules-library,@jahia/vite-pluginpublished at 1.3.1 (latest=1.3.1). The 1.3.0 packages stay on npm and are identical in content📝 Release description curated on the draft release (link on the Publication checklist). Content identical to the abandoned 1.3.0: the 14 changelog fragments since 1_2_0
✅ Chachalog: the
releasebranch is patched — #733 now says v1.3.1 (CHANGELOG heading +.chachalog/.version). Re-verify it still says 1.3.1 right before merging it: anymainpush regenerates it back to 1.3.0🔀 Jahia/jahia-pack-private#1213 re-pinned to 1.3.1, ready for review — merge at publication
ℹ️ History: 1.3.0 was released to staging (run) then abandoned after an issue was found; artifacts reached Nexus, no rollback. Its draft release is deleted, the git tag stays.
mainis now on 1.4.0-SNAPSHOT (normal post-release state)⏭️ Next: stage 4 — QA tests the staged 1.3.1 artifacts per the Tests checklist (matrix: Jahia 8.2.1.x)
[-]Release javascript-modules-engine 1.3.0[/-][+]Release javascript-modules-engine 1.3.1[/+]x0h01 commentedon Oct 16, 2026
Jahia versions used
351593c✅️ Basic install/upgrade/import/e2e checks
✅️ Change-list validations (manual)
npm init @jahia/module@1.3.1 b5-module -- --template hello-world --yes(#715)JCRStoreProviderin the TS types (#790)currentNode.getProvider().getKey()/getMountPoint()/isAvailable()type-check, and an unknown method fails with TS2339jahia-deployexit codes (#813)<JImage>serves resized renditions persrcsetcandidate, andabsoluteon a DAM URL (#786)✅️ Change-list validations (covered by tests)
<JImage>/getImageProps(#789)imageTest, 34 tests: srcset/sizes, density descriptors, alt fallback, SVG, DAMgetUrlchannel, origin prefix. Luxe30-image-rendering,31-srcset-live-integritybuildNodeUrlcache dependencies (#783, #810)cacheDependencyAutocollectTest: flushes the views that built the URL, leaves the opted-out ones, explicit context, included and virtual viewsabsoluteoption (#786, #811)urlHelperTest(content_link_absolute, …)<Island clientOnly>children (#807)reactClientSideTest: hydration, and children hidden while loadingurlHelperTest"should stay inside the edit frame"addCacheDependencyby uuid (#792)cacheDependencyUuidTestreadOnly="children"absolute areas (#680)absoluteAreaTestgqlTest"rendered inside a GraphQL POST request"✅️ Testrail cases // jahia
8.2.1.0,8.2.3.7✅️ Manual UIX exploratory session
Follow up items (not blockers for the release):
📝 Ready for publication.