Skip to content

fix: apply audit hardening across CLI and CI - #5

Merged
continued-agent merged 6 commits into
mainfrom
letta/fix-audit-findings-5d358826
Aug 30, 2026
Merged

fix: apply audit hardening across CLI and CI#5
continued-agent merged 6 commits into
mainfrom
letta/fix-audit-findings-5d358826

Conversation

@letta-integration

Copy link
Copy Markdown

Summary

  • Harden CI workflows and release artifact publication with least-privilege permissions, trusted API smoke tests, exact PR artifact matching, and safe input handling.
  • Improve CLI onboarding for Bedrock and provider-aware setup, persist secrets in protected .env files, and preserve valid custom YAML configuration fields.
  • Fix release packaging/install verification, dependency portability, CLI self-updates, installer checksums, terminal UI regressions, and the accidental focused VS Code E2E test.
  • Add regression coverage for onboarding, YAML updates, UI behavior, and service initialization.

Validation

  • npm test: 157 test files passed; 1,710 tests passed; 5 files and 29 tests skipped.
  • npm run typecheck: passed.
  • npm run lint: passed with two pre-existing warnings.
  • Release build, CLI smoke tests, packed-artifact installation, workflow YAML parsing, shell syntax checks, ShellCheck, and formatting checks: passed.
  • Production dependency audit: 0 vulnerabilities.

The full dependency audit still reports 18 development-only advisories in the semantic-release/npm toolchain. PowerShell parsing was not run locally because pwsh is unavailable.

letta-integration Bot and others added 6 commits August 30, 2026 15:58
Apply the audit findings across CLI configuration, artifact and installer validation, dependency packaging, workflow permissions, and terminal UI regressions, with focused coverage for safe persistence and YAML updates.

👾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta Code <noreply@letta.com>
Invoke npm through the Windows command interpreter without shell command interpolation, provide the read-only token required by FFmpeg metadata setup, and restore the VS Code workbench after each Edit E2E case.

👾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta Code <noreply@letta.com>
Use the FFmpeg release asset currently published by the upstream build repository so JetBrains setup does not download a retired 7.1 archive.

👾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta Code <noreply@letta.com>
Use the maintained pkg fork and Node 20 targets so bundled dependencies requiring modern Node APIs can start in JetBrains integrations.

👾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta Code <noreply@letta.com>
Sync the documentation snapshot from the current base branch so the repository-wide Prettier check passes on the PR merge ref.

👾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta Code <noreply@letta.com>
Keep the formatted README while incorporating the latest base branch so the PR has a clean merge ref.

👾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta Code <noreply@letta.com>
@continued-agent
continued-agent merged commit 29bba2f into main Aug 30, 2026
45 checks passed
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.

1 participant