DX | 31-08-2026 | Release - #364
Open
harshitha-cstk wants to merge 25 commits into
Open
Conversation
DX | 12-08-2026 | Release | Back-merge
Reword the warning logged when a referenced content type is not yet imported so it no longer implies permanent data loss. The reference is deferred and restored later in the same run, so the previous "Removing the field from schema..." wording was misleading. DX-10153 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Per-item environments/locales were collapsed into batch-level arrays, so every item inherited the batch union: backup-dir assets published to every environment found in the backup, and revert unpublished using the first log entry's environments. Batches are now keyed on (locale, environment set). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…rors streamRelease now throws GithubError for HTTP 4xx/5xx responses instead of silently piping the error body (e.g. "404: Not Found") into the zlib decompressor. This was the root cause of the Z_DATA_ERROR crash when the cli-use branch was absent from a repo. extract now attaches an error handler directly on the zlib.createUnzip() stream. Node's pipe() does not forward stream errors, so without this listener a zlib failure emitted an unhandled error event and crashed the process rather than rejecting the Promise cleanly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Moving cliux.loader() (spinner stop) out of finally and into catch before cliux.error() prevents the spinner's carriage-return from wiping the error line. Success path stops the spinner inline after getLatest resolves. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Replace the generic cliux.error+rethrow pattern with a single clean Error throw so oclif prints one message. Message names both the repo and the missing cli-use branch so the developer knows exactly what to check on GitHub. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
GraphQL requests reused the CDA (REST) host and a hardcoded region alias, so any non-default region got a 403 hitting a REST host with a GraphQL query. Resolve the region's actual GraphQL delivery endpoint instead, failing with a clear error when a region has none configured. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
- Add stream.on('error', reject) to handle network/IO failures on the
source stream, not just zlib decompression errors
- Use distinct error message for non-404 HTTP failures (5xx, 403, etc.)
so users aren't told "repo not found" when it's a server/auth error
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Widen CLI_BOOTSTRAP_APP_UNAVAILABLE to cover both repo and branch missing, not just branch, since GitHub returns 404 for both cases - Change status check from >= 400 to < 200 || >= 400 so unexpected non-2xx responses (e.g. stray 3xx) are also rejected as invalid Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…eference-warning fix(import): clarify global field reference-field warning message
- Widen status check from >= 400 to >= 300 so unexpected 3xx responses are rejected before being streamed into extract() - Add regression test asserting a 302 response throws GithubError - Update .talismanrc checksum for github.test.js to reflect new 302 test Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
sinon was used in tests but only available via pnpm workspace hoisting. Adding it explicitly to the package's own devDependencies ensures consistent resolution under strict pnpm module resolution. Version ^21.1.2 matches the standard used across most packages in the monorepo. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
fix(bulk-operations): publish only to scoped targets
fix(tsgen): resolve the real GraphQL endpoint per region
fix(bootstrap): reject on non-2xx tarball response and handle zlib errors
✅ 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
ℹ️ 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:
✅ BUILD PASSED - All security checks passed |
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
4 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.
Bug fixes