chore: point @mat3ra/wode at 2026.8.29-0 - #17
Open
timurbazhirov wants to merge 1 commit into
Open
Conversation
Picks up the execution-unit flavor fix (wode#167): selecting a flavor now takes the input files of the flavor being switched to, instead of carrying over the previous flavor's script.py/requirements.txt and duplicating one of them into the slot a new flavor adds. This package renders that flavor selector via @mat3ra/ave's ExecutionUnit. Most of the package-lock diff is npm refreshing pre-existing stale "dev" metadata, not this bump: a plain npm install on main without any package.json change already produces 303 of those lines. Verified: npm run lint passes, npm run transpile passes, npm run build:standalone passes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XLzSAxuLPHXfvX7BWUsyJB
❌ Deploy Preview for mat3ra-workflow-designer failed. Why did it fail? →
|
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Picks up mat3ra/wode#167, published as
@mat3ra/wode@2026.8.29-0.That fix makes
ExecutionUnit.setFlavortake its input files from the flavor being switched to. Previously the persistedinputrows of the previous flavor were merged into the new flavor's slots — soscript.pykept servinghello_worldcontent whichever python template was picked, and a slot the new flavor adds (utils.pyfor the mattersim templates) was filled with a second copy ofrequirements.txt. This package renders that flavor selector, via@mat3ra/ave'sExecutionUnitinUnitModalContent.@mat3ra/wodemoves from2026.8.18-0to2026.8.29-0in devDependencies; thedependenciesentry stays*.@mat3ra/woveis deliberately left at2026.8.19-0— it carries none of this fix, and moving it would sweep in unrelated changes.On the package-lock diff size
Most of it is not from this bump. A plain
npm install --legacy-peer-depsonmain, with no package.json change at all, already regenerates 303 of those lines — the committed lockfile is stale ondev:metadata. Reproduced both ways before pushing; this bump adds ~11 lines on top.Verification
npm run lint— clean (eslint + prettier)npm run transpile— cleannpm run build:standalone— cleanPre-existing issue noticed, not addressed here
npm testfails 6/6 onmaintoo, with the old wode — unrelated to this change. The tests intests/subworkflowDesignerUpdate.tests.tsimport@mat3ra/workflow-designer/src/utils/...as a package self-reference, but the package declares noexportsfield and there is no matchingtsconfigpath, so the specifier cannot resolve under Node. CI does not surface this because this repo'srun-testsjob only runsValidate JS package— there is no test step, unlike wove/jove which runjs/test.Generated by Claude Code