DX | 13-07-2026 | Release Beta#283
Open
naman-contentstack wants to merge 22 commits into
Open
Conversation
back merge DX | 06-07-2026 | Beta Release
DX - 9364 - docs: comprehensive README audit, package.json standardization, and source fixes
fix: enhance error logging in ImportAssetTypes and ImportAssets
fix: resolve Snyk hardcoded secret false positives in message constants
…ces [DX-9469] pendingVariantAndVariantGrpForExperience was populated with ALL created experience UIDs regardless of whether valid variants were submitted to the API. Experiences with variants:[] never get variant groups from the Personalize backend, so the validation loop timed out and set importData=false, skipping attachCTsInExperience for every experience including valid ones. Fixed by: 1. Adding a versionMap guard in importExperienceVersions (returns boolean) so only experiences that actually submitted variants return true 2. Only adding UIDs to the pending set when importExperienceVersions returns true 3. Adding a null guard in attachCTsInExperience before accessing variantGroup to prevent a silent crash inside Promise.allSettled Note: Bug 2 (missing data-for-variant-entry.json) is not present in v2 — processCleanup always calls createEntryDataForVariantEntry regardless of environments. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Add 11 test cases covering importExperienceVersions returning false for missing file, Lytics-only audiences, and unmapped CS audiences - Add tests verifying Set-based pending list only includes experiences with valid variants submitted to Personalize - Add tests for validateVariantGroupAndVariantsCreated resolving immediately when pending list is empty - Add tests for attachCTsInExperience null guard skipping gracefully when variantGroup is missing - Fix mocha-root-hooks.js to guard loadChalk as optional (not exported in current cli-utilities version) - Fix importExperienceVersions to return false (not undefined) when versions file does not exist, for consistent boolean API Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Message was blaming Lytics audiences specifically but the branch fires for any mapping failure (CS or Lytics). Broadened to "after audience/event mapping". Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…orts [DX-9469] Both were made redundant by the Set-based pending list introduced in the DX-9469 fix. Leaving them risks build failures under noUnusedLocals or ESLint unused-import rules. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
fix(personalize): fix CT linking failure from empty-audience experiences
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
Consider reviewing these vulnerabilities when fixes become available. |
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
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.
No description provided.