fix: six pre-existing integration defects surfaced by the docs audit by waleedlatif1 · Pull Request #7195 · simstudioai/sim

waleedlatif1 · 2026-08-28T03:15:48Z

Six pre-existing defects surfaced by the audit work on #7169. All predate that PR; none is a regression from it. Each is one commit, so any can be reviewed, cherry-picked, or reverted on its own.

What each fixes

fix(github) — file comments were broken in production

github_comment with commentType: 'file_comment' POSTs to /pulls/{n}/comments, where GitHub's OpenAPI lists commit_id as required. It was declared hidden with no subBlock and no mapper write, so nothing could populate it and every request sent undefined → 422. The path is user-reachable: the commentType dropdown offers "File-specific Comment".

Now resolves the PR head SHA when commitId is absent, mirroring the Jira cloudId-from-domain pattern already used in this repo (a harmless lookup request, real work in transformResponse). Applied to both commentTool and commentV2Tool via a shared helper. Also drops position, which GitHub marks "deprecated": true — "This parameter is closing down. Use line instead."

fix(google-drive) — pagination was documented but unreachable

All five list/search tools declared pageToken and forwarded it to Google, but the block had zero occurrences of it in its entire history. Every call was capped at one page while the tools returned a nextPageToken with nowhere to go. Adds a per-operation Page Token field following the block's own existing pageSize/searchPageSize convention, and flips the params to user-only so they are documented.

fix(confluence) — documented a field users could not fill

cloudId was user-only, so it was published across 46 rows, but no subBlock exists. The inverse of the Jira defect. Confluence already resolves the cloud id at runtime — every operation goes through createConfluenceClient, which falls back to getConfluenceCloudId(domain, …) → the shared resolveAtlassianCloudId — so only the visibility was wrong. Marked hidden; domain stays user-settable at all 46 rows.

fix(vanta) — a field whose value was always discarded

The block rendered an advanced MIME Type input and forwarded it, but the upload path never reads it: every return path of downloadServableFileFromStorage yields a non-empty content type, so resolved.contentType always wins. The placeholder claimed it was "used when the file has no type of its own", which never happens.

Removes the subBlock, its mapper write, and its inputs entry, and marks the tool param hidden so it is no longer advertised to the model on a path where it cannot take effect. The param stays, because the base64 branch still reads it. Letting a typed value win instead was rejected: for a compiled artifact the storage-resolved type is the only one matching the bytes actually sent.

fix(docs) — the generator's sort was locale-sensitive

localeCompare with no locale uses the runtime default. Against the real 254 catalog names, tr-TR reorders 141 positions, et-EE 45, cs-CZ 2, and lt-LT diverges at index 40 — so a contributor on any of those regenerates a different integrations.json and fails CI with no obvious cause. Pins en-US at all four sort sites.

fix(docs) — regex literals desynced the source scanner

blankStringsAndComments had no concept of a regex literal, so /don't/ opened a phantom string that swallowed following subBlocks, and /[}]/ closed the enclosing object early. Both returned a short list with no warning — a confident wrong answer, which for the hidden-param filter means silently deleting a user-settable row.

Replaced with a linear scanner that distinguishes a regex literal from a division by the previous significant character, blanks regex bodies whole, and tracks ${} nesting so a backtick inside a template expression cannot end the template early. It now returns null when it ends inside an unterminated construct, and all three call sites treat that as UNKNOWN rather than guessing.

Verification

Every fix has a test proving red→green — reverted, watched it fail, restored, watched it pass.

The two generator fixes leave the generated tree byte-identical, verified by hashing before and after; the warning count is unchanged at 12. Documentation deltas are exactly as intended: Confluence −46, Drive +5, Vanta −1, GitHub 0 (both removed params were already unpublished).

bun run check:audits → 0 · bun run lint:check → 0 · affected suites 380/380.

Notes for review

Drive's pageToken is user-only rather than hidden-with-a-subBlock as google_vault does it. Both produce identical docs and behavior; user-only matches the type's own definition of hidden ("not shown to user or LLM") now that we do show it. One-word change if you prefer vault parity.
The GitHub fix adds one API call per file comment. directExecution would give tighter error control but bypasses the request transport (retry, redirect policy, secret provenance), so the lookup-plus-transform pattern was kept.

localeCompare with no locale argument uses the runtime default, which varies with LANG and the ICU build. Against the real 254 catalog names, tr-TR reorders 141 positions, et-EE 45, cs-CZ 2 and lt-LT diverges at index 40 — so a contributor on any of those regenerates a different integrations.json and fails CI with no obvious cause. Pins en-US at all four sort sites. The committed artifacts are unchanged: regenerating before and after leaves the tree byte-identical. Adds a guard test asserting the committed catalog matches an explicit en-US ordering, plus one that fails if an unpinned localeCompare returns.

The block rendered an advanced MIME Type input and forwarded it as the tool's mimeType, but the upload path never reads it: file-input.ts sets `resolved.contentType || userFile.type || input.mimeType || …`, and every return path of downloadServableFileFromStorage yields a non-empty content type — a literal, getMimeTypeFromExtension's GENERIC_MIME_TYPE fallback, or resolveServableDocBytes' constants and getContentType fallback. The placeholder claimed it was 'used when the file has no type of its own', which never happens. Removes the subBlock, its mapper write and its inputs entry, and marks the tool param hidden so it is no longer advertised to the model on a path where it cannot take effect. The param itself stays, because the base64 branch still reads it. Letting a typed value win instead was rejected: for a compiled artifact the storage-resolved type is the only one matching the bytes actually sent, so an override would break the case the resolver exists to fix.

github_comment sent commit_id as undefined for every file comment: the param was hidden with no subBlock and no mapper write, so GitHub — which marks commit_id required on POST /pulls/{n}/comments — answered 422 on a path the commentType dropdown exposes. When commitId is absent the tool now fetches the pull request first and uses head.sha, mirroring how Jira resolves cloudId from domain. Also removes the position param, which GitHub marks deprecated ("Use line instead"); line is already a real subBlock.

list, search, list_comments, list_permissions and list_revisions each declared a hidden pageToken and forwarded it to Google, but the block had no subBlock of that name and never has — so every list was capped at one page and the nextPageToken output had nowhere to go. Adds a per-operation Page Token field mirroring the block's existing per-operation pageSize fields, collapses them onto the canonical pageToken in the params mapper, and flips the tool param to user-only so it is documented and settable.

All 46 Confluence tools marked cloudId 'user-only', publishing it on 46 doc rows, but the block has no cloudId subBlock so no user could ever fill it. createConfluenceClient already resolves the cloud id from the domain through the shared Atlassian resolver, exactly as Jira does, and Jira marks the same param hidden. Marks cloudId hidden to match. domain stays user-only and settable — it is now the only user-provided param on every Confluence tool.

blankStringsAndComments was a single regex with no concept of a regex literal, so two shapes silently truncated a block's subBlock list: /don't/ the apostrophe opened a phantom string that swallowed the following entries /[}]/ the brace in the character class closed the enclosing object Both returned a short list with no warning — a confident wrong answer, which for the hidden-param filter means silently deleting a user-settable row. No block file uses a regex literal today, so this was latent. Replaces the regex with a linear scanner that distinguishes a regex literal from a division by the previous significant character, blanks regex bodies whole (their last character is arbitrary source, same reason comments are blanked whole), and tracks ${} nesting so a backtick inside a template expression cannot end the template early. The scanner now returns null when it ends inside an unterminated construct. All three call sites treat that as UNKNOWN rather than guessing, so the filter switches off instead of stripping. Generated artifacts are byte-identical and the warning count is unchanged.

…ntegration-defects

vercel · 2026-08-28T03:15:54Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 28, 2026 6:25am

greptile-apps · 2026-08-28T03:20:00Z

Greptile Summary

The PR repairs several integration metadata and execution defects while making documentation generation deterministic and its source scanner more robust.

Moves GitHub commenting to a cancellable, DNS-validated direct-execution path and resolves missing file-comment commit SHAs.
Exposes Google Drive pagination tokens, hides unavailable Confluence and Vanta inputs, and migrates removed Vanta subblocks.
Pins documentation sorting to en-US and improves JavaScript source scanning for regex and template literals.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
apps/sim/tools/github/comment.ts	Implements typed two-phase comment execution, commit-SHA resolution, cancellation propagation, and narrowed provider responses without leaving either previously reported issue outstanding.
apps/sim/tools/github/utils.server.ts	Adds a DNS-validated, IP-pinned GitHub transport that forwards abort signals and strips credentials on cross-origin redirects.
apps/sim/blocks/blocks/google_drive.ts	Adds operation-scoped pagination inputs and maps only the active operation’s token into the tool request.
scripts/generate-docs.ts	Makes generated ordering locale-independent and strengthens lexical scanning of regex and template constructs.

_{Reviews (7): Last reviewed commit: "fix(docs-gen): close a regex-vs-division..." | Re-trigger Greptile}

cubic-dev-ai

All reported issues were addressed across 65 files

_{Reply with feedback, questions, or to request a fix.

Re-trigger cubic}

waleedlatif1 · 2026-08-28T03:57:46Z

@greptile

waleedlatif1 · 2026-08-28T03:57:48Z

@cubic-dev-ai review

cubic-dev-ai · 2026-08-28T03:57:53Z

@cubic-dev-ai review

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

cubic-dev-ai

All reported issues were addressed across 65 files

_{Requires human review: Auto-approval blocked by 6 unresolved issues from a previous review of this commit.

Re-trigger cubic}

…iling field Three corrections to the file-comment fix, from a validation sweep. needsCommitLookup did not check `path`, and ran before the `path` branch in request.url. A file comment with an empty File Path — reachable, since path is not required on the block — went GET /pulls/{n} then POST /comments with path undefined, a 422. On staging it posted to /pulls/{n}/reviews, which GitHub documents as creating a pending review and where commit_id is optional. The lookup is now gated on path, so only a request headed for /comments triggers it. The block has no tools.config.params, so `line` reached the tool as the string the short-input produced while GitHub types it as an integer — file comments would still have 422'd, one API call later. Coerced in request.body, which runs at execution; anything non-finite is omitted rather than sent as NaN. readGitHubErrorMessage returned only the top-level message, so a 422 read "Validation Failed" with no indication of which field was rejected. The errors[] detail is now appended. Responses without errors[] are unchanged.

Adds the file_comment-without-a-path case (which the commit lookup now skips), the untouched-block default where commentType is unset, a pr_comment carrying a path, and the line coercion on both the direct and resolved-commit paths.

A page token is an opaque continuation value produced by a previous tool response, not an account-specific id the user has to supply, so 'user-only' hid it from agent blocks: they saw nextPageToken in the result and could not send it back, silently reporting page one as the whole answer. Every other pagination token in the tool set is 'user-or-llm'. Also covers the case the mapper guard actually defends — a per-operation page token surviving an operation switch, which reaches inputs because shouldSerializeSubBlock skips condition evaluation for advanced fields.

…cannable source - Record why '\\n' is in REGEX_ALLOWED_AFTER: formatters emit a binary '/' at end-of-line, so every line-leading '/' in blocks/*.ts is a real regex, including the ones in table.ts and table_v2.ts. Removing it silently mis-scans those two. - Split a scanner failure out of the spread-only 'ids: null' case. Both scans come back empty for the same reason when blankStringsAndComments bails, so the mapper's renames were dropped with no warning; it now reports a parseError and warns. The spread case is unchanged, and its TSDoc no longer claims a cause that was false. - Route every catalog sort through an exported compareCatalogNames so the ordering test exercises the generator's comparator instead of re-deriving it, and match localeCompare arguments whole so localeCompare() and a variable locale are caught. - Note that downloadServableFileFromStorage guarantees a non-empty content type, so the Vanta mimeType fallback chain reads as deliberately defensive. Artifacts regenerate byte-identically and the generator warning set is unchanged.

waleedlatif1 · 2026-08-28T04:51:58Z

@greptile

waleedlatif1 · 2026-08-28T04:52:00Z

@cubic-dev-ai review

cubic-dev-ai · 2026-08-28T04:52:05Z

@cubic-dev-ai review

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

cubic-dev-ai

All reported issues were addressed across 67 files

_{You’re at about 94% of the monthly reviewed-line limit. You may want to disable incremental reviews to conserve quota. Reviews will continue until that limit is exceeded. If you need help avoiding interruptions, please contact contact@cubic.dev.}

_{Requires human review: Auto-approval blocked because this review re-detected 1 unresolved issue already reported by Cubic.

Re-trigger cubic}

check-block-registry fails a PR that deletes a subblock id without a migration entry, because a deployed workflow can still hold a value under that id. The serializer already discards an orphan silently, but the repo's contract is that the removal is declared rather than inferred. Uses the _removed_ form, scoped to upload_document_file: the value has no replacement field to move to.

The file-comment flow posted its comment from `transformResponse` with a bare global `fetch`, so that request carried no abort signal, no response ceiling and no DNS/SSRF validation — cancelling a workflow still left the comment posted. `transformResponse` cannot receive the signal; `directExecution` can. Both tools now run the lookup and the POST through a new `secureGitHubRequest`, mirroring `secureBitbucketRead`, with the signal forwarded to each. Routing, line coercion and the `errors[]` detail are unchanged, and a failed response still throws an error carrying `status`/`statusText`/`data` as the transport does. Request bodies and the comment payload are explicitly typed instead of `Record<string, any>`.

`mimeType` was marked hidden, but `visibility: 'hidden'` is reserved for system-injected params such as OAuth tokens. It also left the base64 upload path with no way to set a content type, since `fileContent` is hidden too.

The scanner chose regex-vs-division from the previous significant character, so a regex in operand position (`return /x/`, `typeof /x/`, `case /x/`, ...) lexed as a division off the keyword's last letter and its body stayed in the structural view; `azure_devops.ts` is inert today only because the braces in its `return /^\d{4}-\d{2}-\d{2}$/` happen to balance. The `${}` depth counter was also not string-aware, so a brace inside a quoted expression miscounted, the closing backtick was lost and the block was reported unreadable — which silently stops filtering resolver-derived hidden params. Both scans now run on one set of lexer primitives: `${}` expressions are lexed with the same string, comment, regex and template handling as top-level code. Regenerated docs, tool metadata and the integration catalog are byte-identical and the generator's warning count is unchanged.

waleedlatif1 · 2026-08-28T05:19:54Z

@greptile

cubic-dev-ai · 2026-08-28T05:20:00Z

@cubic-dev-ai review

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

cubic-dev-ai

1 issue found across 70 files

Confidence score: 4/5

In scripts/generate-docs.ts, the scanner can classify division after a valid object-literal expression as a regex and return UNKNOWN, which may mis-handle documentation generation for affected inputs; track expression context before treating } as a regex boundary.

_{You’re at about 97% of the monthly reviewed-line limit. You may want to disable incremental reviews to conserve quota. Reviews will continue until that limit is exceeded. If you need help avoiding interruptions, please contact contact@cubic.dev.}

Prompt for AI agents (unresolved issues)


Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="scripts/generate-docs.ts">

<violation number="1" location="scripts/generate-docs.ts:1307">
P2: When a valid object-literal expression is followed by division, this entry misclassifies the division as a regex and makes the scanner return UNKNOWN. Track expression context before treating `}` as a regex boundary, so valid divisions do not disable or alter hidden-parameter filtering.</violation>
</file>

_{Reply with feedback, questions, or to request a fix.

Re-trigger cubic}

secureGitHubRequest passed no redirectPolicy, and the transport only strips credential headers when one is present, so an api.github.com redirect to another origin carried the workspace's Authorization: Bearer header to the new host. Adopts the standard policy already used by the internal Google Drive client. stripAuthOnRedirect stays off: GitHub redirects same-origin for legitimate reasons (a renamed repository answers 301), and dropping auth there would turn a working call into a 401.

toLineNumber ran Math.trunc, so line 3.9 posted the review comment on line 3 — a silent change to what the caller asked for, on a field where landing on the wrong line of the diff is invisible until someone reads the comment. A non-integer now fails with a message naming the field, matching how a missing head commit SHA fails on this path. Blank and unparseable input is still omitted: line is optional and nothing usable was supplied.

The endpoint was chosen by the presence of path, while the body was chosen by commentType, so a pr_comment naming a file posted a review body to POST /pulls/{n}/comments. GitHub documents body, commit_id and path as required there, so that request can only ever 422 — it has been broken since before this PR. The endpoint now follows the comment type: only a file comment carrying a path uses /comments, everything else stays on /reviews. The test that codified the broken routing is corrected, and the full type/path matrix is pinned.

waleedlatif1 · 2026-08-28T05:39:29Z

@greptile

waleedlatif1 · 2026-08-28T05:39:30Z

@cubic-dev-ai review

cubic-dev-ai · 2026-08-28T05:39:37Z

@cubic-dev-ai review

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

cubic-dev-ai

No issues found across 71 files

Confidence score: 5/5

Automated review surfaced no issues in the provided summaries.
No files require special attention.

_{You’re at about 99% of the monthly reviewed-line limit. You may want to disable incremental reviews to conserve quota. Reviews will continue until that limit is exceeded. If you need help avoiding interruptions, please contact contact@cubic.dev.}

_{You've manually re-run cubic several times on this PR. Each manual re-review checks the full PR again and counts toward your usage quota. To preserve your usage limits, we recommend letting cubic automatically review new commits.

Re-trigger cubic}

Removed at request. The visibility change itself is unaffected; it loses only the guard that would have caught a future edit reverting one of the 46 files.

…ected comment POST `secureGitHubRequest` powers the GitHub comment tool's `directExecution` path, which bypasses the declarative transport. Two behaviors the transport provided did not survive the move. User-Agent: the transport sets `User-Agent: Sim` on every request it formats (`request-transport.ts`), and `secureFetchWithPinnedIP` adds none of its own — it builds the request with raw `node:https` and passes headers through verbatim. Production runs on Bun, whose `node:http` shim injects `user-agent: Bun/x.y.z`, so GitHub does not reject these calls today; the defect is that Sim's deliberate attribution is silently replaced by a runtime version string, and that the tool depends on an undocumented runtime behavior that does not hold under Node, where GitHub answers 403 "Request forbidden by administrative rules". Set in the helper rather than in the tool's header map so every future caller inherits it; a caller-supplied value still wins. Redirect method: the policy was `mode: 'standard'`, under which `resolveRedirectHop` rewrites a 301/302'd POST to a bodyless GET regardless of origin. GitHub answers 301 within api.github.com for a renamed repository, so commenting on a PR there would GET `/pulls/{n}/comments`, receive a JSON array, fail the payload shape check, and report success with no comment created. `legacy` keeps the method and body across that hop. Cross-origin credential stripping is unaffected — the guarded follower strips Authorization, Proxy-Authorization and Cookie whenever `sendCredentialsOnCrossOriginRedirect` is false, in either mode.

migrateBlockSubblockIds handles a _removed_ target before it consults whenOperation, so the scope was never applied. Mine was the only _removed_ entry in the file carrying one. Unconditional deletion is also what this case wants. Subblock values are keyed by id and are not cleared when the operation changes, so a user who filled the MIME field and then switched the block to another operation has the value stored under that operation; a scoped delete would strand it permanently. The field no longer exists for any operation, so it should go regardless of the stored operation.

waleedlatif1 · 2026-08-28T06:10:44Z

@greptile review

waleedlatif1 · 2026-08-28T06:10:48Z

@cubic review

cubic-dev-ai · 2026-08-28T06:10:54Z

@cubic review

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

cubic-dev-ai

No issues found across 70 files

Confidence score: 5/5

Automated review surfaced no issues in the provided summaries.
No files require special attention.

_{You’re at about 99% of the monthly reviewed-line limit. You may want to disable incremental reviews to conserve quota. Reviews will continue until that limit is exceeded. If you need help avoiding interruptions, please contact contact@cubic.dev.}

_{You've manually re-run cubic several times on this PR. Each manual re-review checks the full PR again and counts toward your usage quota. To preserve your usage limits, we recommend letting cubic automatically review new commits.

Re-trigger cubic}

…stable `REGEX_ALLOWED_AFTER` was missing `'/'`, so a regex directly after a division operator lexed as a second division: in `x / y / /[}]/` the character class was left in the structural view and its `}` closed the enclosing object early, truncating the block's subBlock ids with no warning. Add `'/'`, and guard the `'+'`/`'-'` entries with a `++`/`--` lookbehind so a postfix update still reads as a value and `i++ / 2` stays a division rather than a phantom regex that runs to end-of-input and reports the block unreadable. The `.`/`#` property guard and the `'\n'` entry both survived their mutants. `counts.in / 2, m: preturn / 2` is self-cancelling — the mis-lexed regex closes on the second slash and blanks nothing structural — so the fixtures now leave an odd number of slashes on the line. The `'\n'` entry had no coverage at all: its fixture is now the wrapped `.match(` newline `/re/` shape that `blocks/table.ts` and `blocks/table_v2.ts` produce, which is what that entry (not the preceding `(`, which the newline overwrites) actually decides. Its comment claimed a count of line-leading regexes that drifts with the sources; restate it without one. Drop the two locale tests that could not fail. CI runs under an `en-US` default, where an unpinned `localeCompare` returns exactly what the pinned one does, so no behavioural comparison discriminates; and asserting the committed `integrations.json` against the comparator that produced it agrees by construction. The source grep for a literal locale argument is the real guard. Generated output is byte-identical and the extraction differential over `apps/sim/blocks/blocks/` is empty.

waleedlatif1 · 2026-08-28T06:19:50Z

@greptile

waleedlatif1 · 2026-08-28T06:19:52Z

@cubic-dev-ai review

cubic-dev-ai · 2026-08-28T06:19:57Z

@cubic-dev-ai review

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

cubic-dev-ai

No issues found across 70 files

Confidence score: 5/5

Automated review surfaced no issues in the provided summaries.
No files require special attention.

_{You’re at about 99% of the monthly reviewed-line limit. You may want to disable incremental reviews to conserve quota. Reviews will continue until that limit is exceeded. If you need help avoiding interruptions, please contact contact@cubic.dev.}

_{You've manually re-run cubic several times on this PR. Each manual re-review checks the full PR again and counts toward your usage quota. To preserve your usage limits, we recommend letting cubic automatically review new commits.

Re-trigger cubic}

waleedlatif1 added 7 commits August 27, 2026 19:54

Merge remote-tracking branch 'origin/staging' into fix/pre-existing-i…

a4d9a73

…ntegration-defects

greptile-apps Bot reviewed Aug 28, 2026

View reviewed changes

Comment thread apps/sim/tools/github/comment.ts Outdated

Comment thread apps/sim/tools/github/comment.ts

vercel Bot deployed to Preview August 28, 2026 03:20 View deployment

cubic-dev-ai Bot reviewed Aug 28, 2026

View reviewed changes

waleedlatif1 added 4 commits August 27, 2026 21:40

cubic-dev-ai Bot reviewed Aug 28, 2026

View reviewed changes

Comment thread scripts/generate-docs.ts Outdated

Comment thread scripts/generate-docs.ts Outdated

vercel Bot deployed to Preview August 28, 2026 04:57 View deployment

waleedlatif1 added 4 commits August 27, 2026 22:01

fix(vanta): keep mimeType an ordinary upload parameter

06bf99f

`mimeType` was marked hidden, but `visibility: 'hidden'` is reserved for system-injected params such as OAuth tokens. It also left the base64 upload path with no way to set a content type, since `fileContent` is hidden too.

vercel Bot deployed to Preview August 28, 2026 05:23 View deployment

cubic-dev-ai Bot reviewed Aug 28, 2026

View reviewed changes

Comment thread apps/sim/tools/github/utils.server.ts Outdated

Comment thread scripts/generate-docs.ts

Comment thread apps/sim/tools/github/comment.ts Outdated

Comment thread apps/sim/tools/github/comment.test.ts Outdated

waleedlatif1 added 3 commits August 27, 2026 22:30

vercel Bot temporarily deployed to Preview August 28, 2026 05:38 Inactive

cubic-dev-ai Bot reviewed Aug 28, 2026

View reviewed changes

test(confluence): drop the cloudId visibility invariant test

e2b4eae

Removed at request. The visibility change itself is unaffected; it loses only the guard that would have caught a future edit reverting one of the 46 files.

vercel Bot temporarily deployed to Preview August 28, 2026 05:49 Inactive

waleedlatif1 added 2 commits August 27, 2026 23:03

vercel Bot temporarily deployed to Preview August 28, 2026 06:05 Inactive

cubic-dev-ai Bot reviewed Aug 28, 2026

View reviewed changes

vercel Bot deployed to Preview August 28, 2026 06:25 View deployment

waleedlatif1 merged commit 46703e3 into staging Aug 28, 2026
30 checks passed

waleedlatif1 deleted the fix/pre-existing-integration-defects branch August 28, 2026 06:31

This was referenced Aug 28, 2026

v0.8.14: files finder, internal routes removal, tools audit, usage tab #7204

Merged

v0.8.16: aws lambda, dynamics 365, actorless run fixes, usage chart #7224

Open

Uh oh!

Conversation

waleedlatif1 commented Aug 28, 2026

What each fixes

Verification

Notes for review

Uh oh!

vercel Bot commented Aug 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

greptile-apps Bot commented Aug 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 5/5

Important Files Changed

Uh oh!

Uh oh!

Uh oh!

cubic-dev-ai Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

waleedlatif1 commented Aug 28, 2026

Uh oh!

waleedlatif1 commented Aug 28, 2026

Uh oh!

cubic-dev-ai Bot commented Aug 28, 2026

Uh oh!

cubic-dev-ai Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

waleedlatif1 commented Aug 28, 2026

Uh oh!

waleedlatif1 commented Aug 28, 2026

Uh oh!

cubic-dev-ai Bot commented Aug 28, 2026

Uh oh!

cubic-dev-ai Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

waleedlatif1 commented Aug 28, 2026

Uh oh!

cubic-dev-ai Bot commented Aug 28, 2026

Uh oh!

cubic-dev-ai Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

waleedlatif1 commented Aug 28, 2026

Uh oh!

waleedlatif1 commented Aug 28, 2026

Uh oh!

cubic-dev-ai Bot commented Aug 28, 2026

Uh oh!

cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

waleedlatif1 commented Aug 28, 2026

Uh oh!

waleedlatif1 commented Aug 28, 2026

Uh oh!

cubic-dev-ai Bot commented Aug 28, 2026

Uh oh!

cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

vercel Bot commented Aug 28, 2026 •

edited

Loading

greptile-apps Bot commented Aug 28, 2026 •

edited

Loading

cubic-dev-ai Bot left a comment •

edited

Loading

cubic-dev-ai Bot left a comment •

edited

Loading

cubic-dev-ai Bot left a comment •

edited

Loading

cubic-dev-ai Bot left a comment •

edited

Loading