Skip to content

fix(settings): stop blaming iam when the aws credentials check fails - #34223

Merged
bolichen97 merged 1 commit into
mainfrom
fix/32095-preflight-not-checked
Nov 19, 2026
Merged

bolichen97 merged 1 commit into
mainfrom
fix/32095-preflight-not-checked

Conversation

@bolichen97

@bolichen97 bolichen97 commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: When the AWS credentials check fails on the Remote Crew set-up checklist, the EC2, CloudFormation and SSM rows say they were not checked yet, instead of blaming a missing permission and offering Copy policy JSON.

On Settings → Remote Crew → Add Crew → Set up a new Crew, a missing AWS CLI, a profile that does not exist, a credential_process helper the CLI cannot find, or a Region the account has not enabled all fail the AWS credentials row. In every one of those runs (#32095) the three service rows then said "Not available with this profile yet — the launch needs permission for this service." and the CloudFormation row offered Copy policy JSON. None of those causes is a permissions problem.

Why it matters

This checklist is the first thing a new user reads on the Remote Crew set-up page, and those four causes are common first-day mistakes. The service rows sent every one of them to an IAM policy, which may need an admin to apply and cannot fix any of the four.

Not a goal

What changed (motivation → approach → change)

When the AWS credentials check fails, the EC2, CloudFormation and SSM rows now read "Not checked yet — needs working AWS credentials first.", with a hollow circle instead of a red error mark, and no row offers Copy policy JSON. When the credentials work and a service call fails, that row keeps its needs-permission sentence, shown as an error notice with Ask the agent, the same way the credentials row shows its failure. Because the three rows share that sentence, the hand-off tells the agent which check failed and which profile and Region it ran with.

The cause: reachability_check (src/kiro_crew/cloud/iam.py) returns as soon as sts get-caller-identity fails, before it calls EC2, CloudFormation or SSM, so their three flags keep their starting false. The checklist drew every false as a missing permission. kirocrew cloud doctor already lists those services only when AWS is reachable; the dashboard now follows the same rule, keyed on the preflight's reachable flag.

EC2 / CloudFormation / SSM row Before After
credentials check failed red error mark, "the launch needs permission for this service", Copy policy JSON hollow circle, "Not checked yet — needs working AWS credentials first.", no Copy policy JSON
credentials work, the service call failed red error mark, needs permission as plain grey text, Copy policy JSON red error mark, the same sentence as an error notice with Ask the agent, Copy policy JSON
credentials work, the service answered check mark, "Reachable with this profile." unchanged

PrereqCard (RemoteCrewPanelSetupCards.tsx) builds the three rows from one helper, and PrereqRow (RemoteCrewPanelLaunch.tsx) accepts ok: null for a row that was not checked. That row keeps its hollow ring while the typed profile or Region differs from the checked one, since it has no verdict to grey out. A failed service row passes its sentence as the row's failure, which PrereqRow already draws through ErrorNotice, plus a failureReport whose detail is the preflight flag that failed and the checked profile and Region, for example {"cloudformation_reachable":false,"profile":"","region":"us-east-1"} ("" is the default profile). The new sentence is in every locale catalog (website/src/i18n/locales/), and the instances spec (docs/system-specs/modules/instances.md) records the rule. Launch stays disabled in that state, and the hint under it still names the AWS credentials row.

Backwards compatibility

Compatible: the preflight API and its JSON are unchanged; only how the setup form draws the three service rows changes, and Launch stays off where it was off before.

Removes nothing: Copy policy JSON still shows whenever the credentials work and CloudFormation is not reachable; it is gone only where no service call ran.

Tests

website/src/test/SettingsRemoteCrewPanelCoverage.test.tsx › "explains an unreachable account and keeps Launch out of reach": with reachable: false, all three service rows say "Not checked yet — needs working AWS credentials first." with neither an error mark nor a check mark, no row says it needs permission, and there is no Copy policy JSON button; after typing another profile, those rows still show the hollow ring.

The same file › "fetches the IAM policy on demand and confirms the copy": with the credentials working and CloudFormation not reachable, the needs-permission sentence sits inside an alert, and that row carries an Ask the agent button. The four existing Copy policy JSON tests (credentials work, CloudFormation does not) keep pinning that the button shows only on a row whose check ran and failed.

The same file › "hands the agent the failed service check, profile and Region": with CloudFormation not reachable, Ask the agent on that row stages a prompt that carries "cloudformation_reachable":false, the Region us-east-1 and the default profile "", and names neither ec2_reachable nor ssm_reachable.

With the two production files put back to the base (6e059d769e), all three tests fail: the first with Unable to find an element with the text: Not checked yet — needs working AWS credentials first., the second with expected null not to be null on its alert check, the hand-off test with Unable to find an accessible element with the role "button" and name /Ask the agent/. With only the mark order put back to grey-before-hollow, the first fails on expect(element).toHaveClass("border-border-strong"). With only the failureReport taken out of serviceRow, the hand-off test fails with expected 'This error just came up in the Kiro C…' to contain '"cloudformation_reachable":false'.

Proof: not provable -- frontend test (prove.py runs Python only)

Determinism: the hand-off test and "explains an unreachable account and keeps Launch out of reach" each passed 20 of 20 runs on their own, and the whole file (61 tests) passed in a shuffled order (--sequence.shuffle --sequence.seed=32095).

Manual verification

The checklist was rendered from this head's built SPA (website/dist) with the dashboard API answered from fixtures: first a profile the AWS CLI cannot find, then working credentials with CloudFormation not reachable. Every claim above was asserted on the page before its screenshot was written. Then Ask the agent was clicked on the failed CloudFormation row and the prompt it staged for the chat was read back; its error report reads:

- Route: /settings/instances
- Request: /api/cloud/preflight
- Source: system
- Message: Not available with this profile yet — the launch needs permission for this service.

{"cloudformation_reachable":false,"profile":"","region":"us-east-1"}

This ran on Linux (Ubuntu 24.04). No real AWS account or gateway was used.

Screenshots / video

Credentials check failed (the profile does not exist), dark and light:

Remote Crew checklist, dark: the credentials row shows the AWS CLI error with a red error mark; EC2, CloudFormation and SSM rows read Not checked yet with a hollow circle and no Copy policy JSON

The same checklist in the light theme

Credentials work and the CloudFormation call failed: that row keeps its red error mark, shows the needs-permission sentence as an error notice with Ask the agent, and still offers Copy policy JSON, dark and light:

Remote Crew checklist, dark: CloudFormation access row with a red error mark, the needs-permission sentence in an error notice with Ask the agent, and the Copy policy JSON button

The same checklist in the light theme

Related Issues

Part of #32095

Sibling sweep

Swept: git grep -nE "_reachable" -- website/src src/kiro_crew/cli_cloud.py src/kiro_crew/cloud/wizard.py
Sibling: src/kiro_crew/cli_cloud.py -- not affected -- cloud doctor prints the three services only inside its reach["reachable"] branch
Sibling: src/kiro_crew/cloud/wizard.py -- not affected -- the launch wizard returns on an unreachable profile before it reads the service flags
Sibling: website/src/pages/settings/RemoteCrewPanel.tsx:961 -- not affected -- the Launch hint names the AWS credentials row first, so it never names a service whose check did not run
Sibling: website/src/pages/ArtifactDeployPage.tsx -- not affected -- it shows only reachable and never draws the S3 or CloudFront flags

Pattern harvest

Not generalizable: one checklist drew rows whose check never ran with the same mark as a check that ran and failed.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@bolichen97
bolichen97 requested review from a team and KiroCrewCaptain as code owners November 9, 2026 23:56
@bolichen97
bolichen97 enabled auto-merge (squash) November 10, 2026 00:17
@github-actions github-actions Bot added the readiness: action required A blocking check or review needs attention label Nov 10, 2026
@github-actions

github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of d38014ae95b1518f03e840cdeb038420fc59804e — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks. reachability_check returns before it makes any service call when sts fails, so treating reachable: false as "not checked" matches the backend's actual behaviour and what cloud doctor already does.

Notes

  • Whether a service row was checked is inferred from reachable on the dashboard side. If reachability_check ever runs a service probe after an sts failure, these rows will silently hide a real denial. The spec paragraph pins this coupling, but a backend test that names it would make the dependency explicit.

[DESIGN-REVIEWED] d38014a

Description read

[DESCRIPTION-READ] 8e7ef19defb00039d2635b49d2aa5c595206172df62fd51c973e01f5692debed

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of d38014ae95b1518f03e840cdeb038420fc59804e — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

When the credentials row fails, the three service rows now say they were not checked, which fixes the cause. One item that goes beyond the Goal is listed as a note.

Notes

  • Item 4 — rides along / oversized: the Goal covers only the case where "the AWS credentials check fails", but the "credentials work, the service call failed" row also changes: the sentence becomes an error notice with Ask the agent and a hand-off report (serviceFailureReport). No issue or user report is cited for it. Subtraction: delete serviceFailureReport, and in that branch keep { ok: false, detail: service_missing }; the hand-off test goes with it.

What this change ships

Inventory (6 items) — 5 justified

Intent: a new user whose AWS credentials fail is not sent to an IAM policy that cannot fix the problem. This is a FIX.

  1. When the credentials check fails, the EC2, CloudFormation and SSM rows read "Not checked yet — needs working AWS credentials first." — justified
  2. Those rows show a hollow ring instead of a red X, and keep it when the profile or Region is edited — justified
  3. Copy policy JSON is hidden when no CloudFormation call ran — justified
  4. When the credentials work and a service call fails, the row shows an error notice with Ask the agent and a report naming the check, profile and Region — rides along, outside the Goal
  5. A new service_not_checked string in 14 locale catalogs — justified
  6. The instances spec records the not-checked rule — justified

[FIRST-PRINCIPLES-REVIEWED] d38014a

Description read

[DESCRIPTION-READ] 0c5b43c7424458ca29f746428ef2da6579f13b226c291bd8d5cfd670266e9140

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

UX-level review of d38014ae95b1518f03e840cdeb038420fc59804e — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

UX-Verdict: PASS

Nothing blocks. The blind reader read the new "Not checked yet — needs working AWS credentials first." rows and the hollow ring correctly as "waiting until the first one passes", and every changed state appears in the four screenshots.

Notes

  • The blind reader rated Ask the agent on the failed CloudFormation row only "a guess" and could not tell whether it "sends the message straight away or just fills it in". The same reused link now sits on two rows. This is a follow-up, not a fix for this PR.
  • The blind reader saw "Using your default AWS credentials" next to rows that say "with this profile" and asked "which profile is being used". That wording predates this PR, but the PR now puts service_missing in the error notice, so the confusion is more visible. A follow-up could name the profile in service_ok and service_missing.

[UX-REVIEWED] d38014a

Description read

[DESCRIPTION-READ] a5792a7acc04fc118b94eb69356f06e6343812e9421da66519533e365e6650c3

That sha256 names everything this verdict read: the PR description, plus the 7 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed d38014ae95b1518f03e840cdeb038420fc59804e — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] d38014a

Verdict parsed from the review's SHA-scoped output markers for commit d38014ae95b1518f03e840cdeb038420fc59804e.

False positive or not applicable? A repository writer can comment:
/ai-review override fable d38014ae95b1518f03e840cdeb038420fc59804e false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of d38014ae95b1518f03e840cdeb038420fc59804e and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] d38014a

False positive or not applicable? A repository writer can comment:
/ai-review override gpt d38014ae95b1518f03e840cdeb038420fc59804e false-positive: <reason, 20 to 500 characters>

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 10, 2026
buluoray
buluoray previously approved these changes Nov 10, 2026

@buluoray buluoray left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve on ac08be0. With a failed AWS credentials check, the EC2/CloudFormation/SSM rows now say "Not checked yet" with a hollow mark and no Copy policy JSON, instead of blaming a missing permission; the reachable branch is unchanged. Decisive lines: website/src/pages/settings/RemoteCrewPanel.tsx:894, website/src/pages/settings/RemoteCrewPanel.tsx:1426, website/src/pages/settings/RemoteCrewPanelLaunch.tsx:575, src/kiro_crew/cloud/iam.py:1148

@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 10, 2026
@bolichen97
bolichen97 force-pushed the fix/32095-preflight-not-checked branch from ac08be0 to 76d0a6a Compare November 10, 2026 22:44
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in website/src/pages/settings/RemoteCrewPanel.tsx, website/src/pages/settings/RemoteCrewPanelLaunch.tsx and website/src/test/SettingsRemoteCrewPanelCoverage.test.tsx since this head went green (2caa69b -> b7b7b6c); CI re-running.

[operator: bolichen97]

@github-actions github-actions Bot removed the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 10, 2026
@KiroCrewCaptain

KiroCrewCaptain commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

Code change approver recommendation: A person should decide

Why: the decider estimates an 8% chance that this change introduces a defect, within the 12% limit for approving on its own, but it is held at tier pending: being reviewed.

The PR's main claim holds up. iam.reachability_check returns as soon as sts get-caller-identity fails, before it calls EC2, CloudFormation or SSM. api_cloud_preflight passes that result through unchanged. So when reachable is false, the three service flags are false only because they never ran, and keying the "Not checked yet" rows on preflight.reachable is correct.

Launch is still gated as before: blockingCheck in RemoteCrewPanel.tsx is unchanged and names the credentials row first.

Copy policy JSON now shows only when the credentials work and the CloudFormation call actually ran and failed. A failed service row's sentence moves into failure, which PrereqRow already draws as an error notice with Ask the agent. Its failureReport follows the same shape as the existing refusalReport helper. It carries only the flag name, the profile name (the UI already says the profile name is the only thing it uses) and the Region, so no secrets go out. ErrorNotice only uses the report when Ask the agent is clicked, so nothing is added to the error journal when the row is drawn.

PrereqRow now accepts ok: boolean | null. Every other caller still passes a boolean, and the

Tier: pending: being reviewed.

An automated recommendation, not a review: a maintainer still decides. It approves on its own only when the estimated chance of a defect is at most 12% and the change has at most 400 changed lines. Decider v3c (217fe607) · commit d38014ae95 · 104 changed lines. If this recommendation is wrong, reply here: replies are how the approver is evaluated.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: checking Automated validation is still running labels Nov 10, 2026
@bolichen97
bolichen97 force-pushed the fix/32095-preflight-not-checked branch from 76d0a6a to b96feeb Compare November 11, 2026 22:50
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 11, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in docs/system-specs/modules/instances.md and the 13 website/src/i18n/locales/*.json catalogs since this head went green (b7b7b6c -> 23b63d2); CI re-running.

[operator: bolichen97]

@bolichen97

bolichen97 commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor Author

self-added: yes
mechanism: serviceRow sends a failed service probe through PrereqRow's failure prop

  • Route failed service probes through ErrorNotice span=8d38b38ea858

fixed in b96feeb: when the credentials work and an EC2, CloudFormation or SSM call fails, serviceRow passes the needs-permission sentence as PrereqRow's failure, which renders it through ErrorNotice with askAgent; the not-checked and reachable rows keep detail.
Copy policy JSON stays keyed on cloudformationRow.ok !== false, so it shows exactly when the CloudFormation call ran and failed.
Test: "fetches the IAM policy on demand and confirms the copy" asserts the sentence sits in a role="alert" notice with an Ask the agent button in that row; on the base code it fails with expected null not to be null.

[operator: bolichen97]

@github-actions github-actions Bot removed the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 11, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

[operator: bolichen97] The red Backend Tests shards on this head (3.12 shards 5 and 6, Windows shard 4) and the Coverage Gate that fails closed behind them are red on main too, with the same node ids (main run on e8283ce). This PR touches neither file:

Analyze (javascript-typescript) failed uploading its results on an API rate limit, an infrastructure red. This PR waits for those two fixes, then re-syncs onto them and re-runs CI.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Nov 12, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

[operator: bolichen97] Both test reds on this head are fixed on main by #35625: test/test_wait_discipline_ratchet.py::test_the_scan_matches_known_sites and test/test_updates_handlers_facade.py::test_every_name_served_from_outside_the_family_is_visible_to_type_checkers (the Coverage Gate fails closed behind them). Main now carries one other backend red, test/test_cloud_launch_customize.py::TestAmiArchitectureCheck::test_matching_architecture_proceeds_to_deploy (#35745, fix in #35746, approved). This branch re-syncs once #35746 lands, so its next run is measured against a main that carries both fixes; a re-sync now would go red on that test and need a second one. The CodeQL JavaScript red is a CI API rate limit; the re-sync push re-runs it.

buluoray
buluoray previously approved these changes Nov 12, 2026

@buluoray buluoray left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve on b96feeb. When the AWS credentials check fails, the EC2, CloudFormation and SSM rows now say "Not checked yet" with a hollow mark and offer no policy to copy, so the page no longer tells the user to fix an IAM permission. A service call that did run and fail is now shown as an error notice with an Ask the agent button. The red test shards on this head are failures that main already had and has since fixed, so the PR needs a rebase before it can go green. Decisive lines: website/src/pages/settings/RemoteCrewPanel.tsx:906-910, website/src/pages/settings/RemoteCrewPanel.tsx:1451-1453, website/src/pages/settings/RemoteCrewPanelLaunch.tsx:545, website/src/pages/settings/RemoteCrewPanelLaunch.tsx:582-583, src/kiro_crew/cloud/iam.py:1194

@bolichen97
bolichen97 force-pushed the fix/32095-preflight-not-checked branch from b96feeb to 3a954af Compare November 13, 2026 13:11
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in website/src/pages/settings/RemoteCrewPanel.tsx, docs/system-specs/modules/instances.md and the 13 website/src/i18n/locales/*.json catalogs since this head went green (23b63d2 -> c22557c); CI re-running.

The new base carries #35625, which fixed the two test reds the previous head inherited from main (test/test_wait_discipline_ratchet.py::test_the_scan_matches_known_sites and test/test_updates_handlers_facade.py::test_every_name_served_from_outside_the_family_is_visible_to_type_checkers). The commit's patch is unchanged (range-diff =), and the four screenshots in the description were re-captured from this head.

[operator: bolichen97]

@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 18, 2026
When the Remote Crew credentials check fails, reachability_check never
calls EC2, CloudFormation or SSM, so their flags stay false. The setup
checklist painted every false as a missing permission and offered Copy
policy JSON, sending a user with no AWS CLI or a mistyped profile to an
IAM policy that cannot help.

With reachable false the three service rows now show a neutral hollow
circle, say they were not checked yet because the credentials have to
work first, and offer no policy to copy. PrereqRow takes ok: null for
that state; the new line is translated in every catalog, and the
instances spec records the rule. A service call that did run and fail
shows its needs-permission line through the row's error notice, with
the agent hand-off, as the credentials row already does. That hand-off
names the failed check and the checked profile and Region.

Part of #32095
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in website/src/pages/settings/RemoteCrewPanel.tsx, website/src/pages/settings/RemoteCrewPanelLaunch.tsx, website/src/test/SettingsRemoteCrewPanelCoverage.test.tsx, docs/system-specs/modules/instances.md and the 13 website/src/i18n/locales/*.json catalogs since this head went green (c22557c -> 6e059d7); CI re-running.

Main moved the AWS checklist into PrereqCard (website/src/pages/settings/RemoteCrewPanelSetupCards.tsx), so the three service rows moved there with it; the change to what they show is the same.

[operator: bolichen97]

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Nov 19, 2026

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed head d38014a. When the AWS credentials check fails, the EC2, CloudFormation and SSM rows now say they were not checked yet, with a hollow mark and no Copy policy JSON. This matches the backend: the reachability check returns before it makes any service call when the identity lookup fails, so those flags were never really checked. When the credentials work, a failed service row still shows its needs-permission notice with a hand-off that names the failing check and the profile and Region it ran against. Copy policy JSON still shows only when the CloudFormation call ran and failed. Launch gating is unchanged, the new tests pin both states, and the frontend tests and type check pass on this head, so nothing blocks.

@bolichen97
bolichen97 merged commit 21c9a40 into main Nov 19, 2026
101 checks passed
@bolichen97
bolichen97 deleted the fix/32095-preflight-not-checked branch November 19, 2026 10:53
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants