DX | 10-08-2026 | Release - #393
Open
OMpawar-21 wants to merge 710 commits into
Open
Conversation
…es-coverage Fix/dx 3674 improve testcases coverage
…oints-region Revert "feat: implement download script for regions.json and update postinsta…"
- Fix all failing test suites (632 tests now passing) - Add 21 new comprehensive test suites covering: * Asset management, cache & persistence * Complex queries, deep references, field projections * Global fields, JSON RTE, live preview * Metadata, modular blocks, multi-reference * Pagination, performance benchmarks * Query encoding, operators, sync operations * Taxonomy queries - Fix TypeScript errors (TS18048, TS2304, TS2554, TS1128, TS1005) - Fix Axios errors (422, 400) with graceful error handling - Fix circular references in deep reference chains (WeakSet tracking) - Fix flaky performance tests (network variance handling) - Add global console.error suppression for SDK validation (jest.setup.ts) - Remove redundant synchronization.spec.ts (superseded by comprehensive version) - Update .gitignore to exclude build artifacts - Sync with latest development (19 commits) - Remove @nrwl/jest dependency (from upstream) Test Results: Test Suites: 39 passed, 39 total (100%) Tests: 632 passed, 632 total (100%) Status: Production Ready Breaking Changes: None Security: All credentials use environment variables
…emove deprecated regions.json file.
…or messages for invalid regions
…tentstackEndpoint refactor: region handling logic to utilize getContentstackEndpoint. …
…tentstackEndpoint chore: 🗑️ remove redundant code
Enh: add type casting helper for BaseQuery methods to return Query type
Fix/update dependency
fix version bump
Development
DX | 12-11-2025 | Release
…ation fix: reverts the endpoints helper method integration
…ry, and Query classes for better clarity and user guidance.
…ze centralized error messages for improved consistency and clarity.
- Add browser environment test suite (jsdom) * Import validation tests * Initialization tests with real .env credentials * Dependency safety checks (catches fs/path/crypto usage) * Real API call tests using existing .env - Add bundle validation scripts * validate-browser-safe.js: Scans bundles for Node.js-only APIs * test-bundlers.js: Validates bundler compatibility - Add test configurations * jest.config.browser.ts: Browser environment Jest config * jest.setup.browser.ts: Browser test setup * playwright.config.ts: Real browser testing (structure) - Update package.json with new npm scripts * test:browser: Run browser environment tests * test:all: Run all tests (unit + api + browser) * validate:browser: Validate bundle safety * validate:bundlers: Test bundler compatibility - Update .gitignore * Add .env to prevent credential leaks * Adjust docs/ pattern This implements AWS SDK v3-style multi-environment testing to catch Node.js-only API usage (fs, path, crypto) before production, preventing customer build failures in browser environments.
Added Branches support in entry variants
Reporting: - Add request-capture plugin, assertion tracker, and a single-file HTML reporter that shows per-test SDK method, API request, copy-paste cURL, request/response, and Assertions Verified (expected vs actual) inline. Gated by ENABLE_HTTP_CAPTURE; tokens masked. Wired into jest config/setup. - Fix stale console-error suppression to match the current SDK message. Test fixes: - Reference specs use complex_all_fields fields (single_ref/multi_ref/self_ref). - Sync token assertions handle both no-change (stable) and change (advanced) cases. - Asset dimension asserts on an image asset; raise slow error-path test timeout. Bundlers: - run-with-report.sh: regenerate lockfile, surface install errors, fix counting. - Pin webpack to 5.108.0 (5.109 resolver regression with @ljharb transitive deps). .talismanrc: whitelist the 4 new/updated report+bundler files (false positives).
…-suite-fixes test: rich HTML report + API suite fixes for enriched v5 stack
DX | 29-07-2026 | Release
chore: back-merge main into development
Transient network-layer errors (ENOTFOUND, ENETUNREACH, ECONNRESET, ECONNREFUSED, EAI_AGAIN, ETIMEDOUT, EHOSTUNREACH, ENETDOWN) now trigger the SDK's configured retry policy instead of failing immediately. A combinedRetryCondition composes the user-supplied retryCondition with the new default network-error check. The user condition runs first; if it throws, a warning is emitted via logHandler and the SDK falls back to the default. The original config object is never mutated. ECONNABORTED is excluded — @contentstack/core classifies it as a structured TIMEOUT error and handles it separately. Resolves: SF Case #00060601 (SentinelOne) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…warnings Lines 182 and 184 in contentstack.ts (the catch block and logHandler warn path) were flagged uncovered by jest-coverage-report-action. Added test (g) which exercises a retryCondition that throws, verifies the SDK falls back to default retry behaviour, and asserts the warning is emitted via logHandler. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…and package-lock.json
DX | 03-08-2026 | Release
back merge
…age gap
- Fix misleading comment: only the retryCondition composition avoids
mutation; config.host is still mutated elsewhere in the function
- Emit a structured logHandler payload ({ type, message, error }) when
retryCondition throws, consistent with request/response interceptors
- Add !error.response guard to isTransientNetworkError so it only retries
errors that arrived before any HTTP response, matching the JSDoc contract
- Add tests (h1, h, k) to cover the ?? fallback branch, the logHandler?.
undefined branch, and the user retryCondition returning true; branch
coverage on contentstack.ts: 93.88% → 97.95%
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Bumps @contentstack/core to ^1.5.1, which fixes MODULE_NOT_FOUND / "expression is too dynamic" build failures in bundlers (Next.js/Turbopack, webpack) and native ESM ReferenceErrors from the keep-alive agent setup. NOTE: do not publish until @contentstack/core 1.5.1 is live on npm, or the ^1.5.1 range will not resolve. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…-1.5.1 chore: Prepare 5.5.2 release with @contentstack/core ^1.5.1
DX | 05-08-2026 | Hotfix
chore: back-merge main into development
…oc accuracy - Add release date (Aug-05-2026) to the 5.6.0 CHANGELOG entry - Update @returns JSDoc on isTransientNetworkError to reflect both conditions: error.code match and absence of error.response Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
fix(DX-10060): retry transient network errors to prevent build crashes
Force push on main after PR#389/PR#390 broke shared ancestry. Preserves DX-10060 (network error retry) from development. Adds snyk false-positive suppression from main.
chore: reconcile diverged git histories
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
Coverage report
Test suite run success720 tests passing in 36 suites. Report generated by 🧪jest coverage report action from b83159c |
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
14 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.
No description provided.