fix: respect excludeContentTypes across instances sharing a type_prefix

[abhishek-ezhava-cstk]

Summary

Fixes DX-9470. A customer reported that excludeContentTypes is silently ignored when two gatsby-source-contentstack instances share the same type_prefix (e.g. a main stack + a shared/publisher stack merged into one schema). Customer opened PR #277 with a fix; per policy we don't merge code from an external fork directly, so this reimplements the fix ourselves after verifying the root cause and the intended behavior independently.

Root cause: Gatsby's plugin cache is shared across all instances of this plugin, not namespaced per instance/options. The content-types list was cached under a bare type_prefix key (unlike most other cache keys in this codebase, which already suffix with api_key). When two instances share type_prefix, whichever instance's createSchemaCustomization runs last overwrites that key for both, so the instance with excludeContentTypes reads back the other instance's unfiltered list.

Fix:

• Namespace the content-types cache key by api_key at all 5 read/write sites (create-schema-customization.js, create-resolvers.js, entry-data.js x2, source-node.js) — this is the root-cause fix, not a re-filter patch at a couple of call sites.
• contenttype-data.js: excluded content types no longer sneak back in via a reference field on an included content type (FetchUnspecifiedContentTypes's referred-content-types lookup wasn't filtered by excludeContentTypes).
• Dependency hygiene: patched fast-uri, brace-expansion, postcss to their fixed versions, and deduped @semantic-release/npm to remove a duplicate older/vulnerable branch pulled in by semantic-release's own dependency tree.

Test plan

• New unit test (src/tests/exclude-content-types.test.js): two configs sharing a type_prefix with different api_keys and different excludeContentTypes no longer collide; referred-content-types filter verified in isolation.
• npm test — full suite passes.
• Live end-to-end verification against two real Contentstack stacks sharing a type_prefix, each with its own excludeContentTypes, using the contentstack-gatsby-starter-app:
  • Ground-truth entry counts pulled directly from each stack's CDA.
  • After the fix, the merged GraphQL type only contains the non-excluded stack's entries — verified exact match, no cross-stack leakage.
  • Added a real reference field (included type → excluded type) with live data — confirmed the excluded type's schema type name still appears (expected, required for the reference field's GraphQL type), but zero real entries/nodes are sourced for it, and the reference resolves empty.
  • Full Playwright e2e suite (28 tests) passes with both single-stack and two-stack configs.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	1	10	✅ Passed
🟠 High Severity	0	2	25	✅ Passed
🟡 Medium Severity	0	41	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	0	90 / 365 days	✅ Passed
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ 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:

• Critical without fixes: 1
• High without fixes: 2
• Medium without fixes: 41
• Low without fixes: 0

✅ BUILD PASSED - All security checks passed

[Copilot]

Pull request overview

This PR fixes a multi-instance caching collision in gatsby-source-contentstack where excludeContentTypes could be ignored when two plugin instances share the same type_prefix, by namespacing the cached content-types list with api_key. It also tightens excludeContentTypes behavior for referred content types and updates dependency overrides/lockfile accordingly.

Changes:

• Namespace the cached content-types list key as ${type_prefix}_${api_key} across all read/write sites to prevent cross-instance cache overwrites.
• Ensure referred content types fetched via reference fields don’t reintroduce content types listed in excludeContentTypes.
• Add unit coverage for the cache isolation + referred-content-types filtering, and update dependency overrides / lockfile.

Reviewed changes

Copilot reviewed 8 out of 10 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/create-schema-customization.js	Writes the content-types cache entry using a key that includes api_key.
src/create-resolvers.js	Reads content types from the namespaced cache key.
src/entry-data.js	Reads content types from the namespaced cache key in both entry-fetch flows.
src/source-node.js	Reads content types from the namespaced cache key during sourcing.
src/contenttype-data.js	Filters referred content types using excludeContentTypes.
src/tests/exclude-content-types.test.js	Adds unit tests for cache key isolation and referred-type filtering.
tests/exclude-content-types.test.js	Compiled/built copy of the new unit tests.
package.json	Bumps version and updates overrides (incl. patched dependency versions / dedupe).
package-lock.json	Lockfile updates reflecting the dependency/override changes.
.talismanrc	Adds checksum allowlists for newly changed files (flagged in review).

Files not reviewed (1)

• tests/exclude-content-types.test.js: Generated file

Suppressed comments (1)

.talismanrc:13

• .talismanrc: Checksum allowlists for test files also bypass Talisman scanning for those files when the checksum matches. If these were added due to a false positive, it’s safer to address the triggering content or apply a narrowly-scoped ignore rather than allowlisting entire files by checksum.

- filename: src/tests/exclude-content-types.test.js
  checksum: 4acbcfad3da0e20b6150ce47054668b629db9ddd8362d3a96fadb3a770a0f5a4
- filename: tests/exclude-content-types.test.js
  checksum: 907f5d9ee53a42774f4ecbc361dc6b2cd6f278ed7dbf6dd6cf071d4f478a4b67

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.