chore(deps): bump doenetml-iframe and v06-to-v07 to 0.7.27 - #3043
Merged
Merged
Conversation
Picks up the improved v06-to-v07 conversion script, which is bundled into the app rather than loaded from the CDN. @doenet/assignment-viewer takes doenetml-iframe as a peer dependency and imports it as an external, so it renders with 0.7.27 too without needing a republish. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Bumps
@doenet/doenetml-iframeand@doenet/v06-to-v07from^0.7.24to^0.7.27inapps/app, and@doenet/doenetml-iframeinapps/web.Why
The motivating change is
@doenet/v06-to-v07. Unlike the engine, it is not CDN-loaded — it is dynamically imported and bundled into the app (apps/app/src/paths/editor/DoenetMLVersionComponents.tsx:155), so the improved v06→v07 conversion script in 0.7.27 only arrives by bumping the package.@doenet/doenetml-iframegoes along with it to keep the wrapper in lockstep with the 0.7.27 engine.Note on which engine actually runs
doenetml-iframedoes not contain the engine. It builds a CDN URL from thedoenetmlVersionprop:fed from
doenetmlVersions.fullVersion(AssignmentViewer.tsx:600,ActivityViewer.tsx:362). So the production DB row is the real lever for the engine version and is not part of this PR. The seed already maps0.7→fullVersion: "latest", so dev picks up 0.7.27 with no change.@doenet/assignment-vieweris unaffectedIt does not need a republish to render with 0.7.27:
@doenet/doenetml-iframeis a peerDependency (^0.7.24), not a dependency — the pinned0.7.24in its manifest is only a devDependency for its own build/test.dist/index.jsimports exactly two externals,reactand@doenet/doenetml-iframe. Nothing is bundled, so there is no second copy.npm hoists the single copy resolved from
apps/app, so assignment-viewer now renders through 0.7.27.^0.7.24accepts 0.7.27, so there are no peer warnings.Verification
npm run build:ts— cleannpm run build:assets— app and web both buildnpm run lint:check— clean across all workspacesWorth a manual smoke test of a real assignment, since assignment-viewer was built against the 0.7.24 wrapper's prop/postMessage surface.
🤖 Generated with Claude Code