refactor: bump experience example apps to app-sdk 4.68.1 (ExO rename) [PROD-3331] - #11260
Merged
Merged
Conversation
Bump @contentful/app-sdk to ^4.68.1 in examples/experience-toolbar and examples/experience-auditor. 4.68.1 is the latest published release and ships the ExO M2 terminology rename: ExperienceNodeType and ExperienceContext.type are now supersets that accept both legacy (Fragment/InlineFragment) and canonical (ExperienceFragment/ InlineExperienceFragment, experienceFragment) vocabulary, and ExperienceSnapshot gains an ExperienceFragment arm. Both apps consume the rename transitively via the typed sdk.experiences.* surface (no hardcoded CMA routes or entity-type-string comparisons), so no source changes were required: - context.type === 'experience' comparison in experience-toolbar still type-checks against the widened union; experienceFragment groups with fragment on the secondary badge, which is correct. - node.nodeType / ExperienceNodeType usages resolve against the widened union with no changes. Verified against 4.68.1: both apps typecheck (tsc --noEmit, exit 0), build (vite build), and pass their full test suites (toolbar 11/11, auditor 38/38). No behavioral regression. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Joe Bingham (jshmo)
changed the title
Jared Jolton (jjolton-contentful)
approved these changes
Aug 4, 2026
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
2 participants
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.
What
Bumps
@contentful/app-sdkto^4.68.1(latest published;5.0.0is alpha-only) in the two Experiences example apps:examples/experience-toolbarexamples/experience-auditorResolves PROD-3331.
Why
4.68.1 ships the ExO M2 Terminology Update rename. The relevant public types widened to accept both legacy and canonical vocabulary:
ExperienceNodeType→'Component' | 'Fragment' | 'ExperienceFragment' | 'InlineFragment' | 'InlineExperienceFragment' | 'Slot'ExperienceContext.type→'experience' | 'fragment' | 'experienceFragment'ExperienceSnapshotgains anExperienceFragmentarm (sys.component/Contentful:Component)Both apps consume the product exclusively through the typed
sdk.experiences.*surface — no hardcoded CMA routes, no entity-type-string comparisons against removed values — so they're only affected transitively. No source changes were required.AC verification
@contentful/app-sdkbumped to the rename version in both apps (resolves to 4.68.1).tsc --noEmit, exit 0), build (vite build), and pass their existing suites — toolbar 11/11, auditor 38/38.context.type === 'experience'comparison inExperienceToolbar.tsxverified against the widened public union: it still type-checks; the newexperienceFragmentvalue groups withfragmenton thesecondarybadge, which is the correct behavior. Left unchanged per the "update only if the SDK changed that contract" guidance.node.nodeType/ExperienceNodeTypeusages resolve against the widened union unchanged.Out of scope
No changes to shipped first-party/partner apps or
marketplace-listing-api; not owning the SDK rename itself.🤖 Generated with Claude Code