feat: add upgrade notification when newer CLI version is available by gonengar · Pull Request #157 · base44/cli

gonengar · 2026-01-30T14:22:45Z

Note

Description

This PR adds automatic upgrade notifications to the Base44 CLI. When users run any command, the CLI checks for newer versions on npm and displays a notification immediately after the banner if an upgrade is available. The implementation includes defensive error handling to ensure version checks never disrupt user workflows, with a 500ms timeout and CI environment variable to prevent interference with npm operations. Additionally, this PR introduces a centralized test override mechanism (BASE44_CLI_TEST_OVERRIDES) using Zod schemas for type-safe runtime validation, enabling comprehensive testing of behaviors that cannot be mocked with vi.mock() due to the bundled distribution architecture.

Related Issue

None

Type of Change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Documentation update
Refactoring (no functional changes)
Other (please describe):

Changes Made

Upgrade Notification Feature:

Added version-check.ts utility that fetches latest version from npm registry using execa with 500ms timeout and CI=1 environment variable
Created upgradeNotification.ts that formats and displays upgrade notifications using theme's shiny orange color
Integrated upgrade check into runCommand.ts to display notifications after banner, before command execution
All errors are silently caught to prevent disrupting CLI workflows (network failures, timeouts, npm unavailability)
Notification format: Update available! 0.0.26 → 1.0.0 Run: npm update -g base44

Test Infrastructure Improvements:

Introduced BASE44_CLI_TEST_OVERRIDES environment variable for centralized test mocking via JSON
Created TestOverridesSchema in src/core/project/schema.ts using Zod with runtime validation via .safeParse()
Added getTestOverrides() utility in src/core/config.ts for shared, type-safe access to test overrides
Refactored app-config.ts to use the shared getTestOverrides() utility, consolidating test override logic
Extended CLITestkit with givenLatestVersion() method and improved environment variable snapshot handling
Added toNotContain() matcher to CLIResultMatcher for negative assertions in tests
Added comprehensive tests in tests/cli/version-check.spec.ts covering three scenarios: newer version available, current version (null), and no override

Documentation:

Updated AGENTS.md with detailed "Test Overrides" section documenting the BASE44_CLI_TEST_OVERRIDES pattern
Documented step-by-step guidelines for extending the override mechanism with new fields
Explained why vi.mock() doesn't work with bundled code (path aliases resolved at build time)
Added testing rule feat(login) - mock implementation #5: "Use test overrides - Extend BASE44_CLI_TEST_OVERRIDES for new testable behaviors; don't create new env vars"

Testing

I have tested these changes locally
I have added/updated tests as needed
All tests pass (npm test)

Checklist

My code follows the project's style guidelines
I have performed a self-review of my own code
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation (if applicable)
My changes generate no new warnings
I have updated AGENTS.md if I made architectural changes

Additional Notes

Error Handling Philosophy:
The implementation gracefully handles all failure scenarios. If npm is unavailable, the registry is unreachable, or the command times out (500ms), the notification is silently skipped without any impact on the user experience. This ensures the version check never becomes a point of failure for CLI operations.

Test Override Architecture:
Tests run against bundled dist/index.js where path aliases (@/) are resolved at build time, making vi.mock("@/some/path.js") ineffective. The BASE44_CLI_TEST_OVERRIDES pattern provides a runtime override mechanism that works with bundled code and is now documented with Zod schema validation for type safety. This approach is extensible for future testing needs.

Performance Considerations:

500ms timeout prevents hanging on slow networks
CI=1 environment variable prevents npm from interfering with package operations
Async execution doesn't block command startup

_{🤖 Generated by Claude | 2026-02-03 09:30 UTC}

github-actions · 2026-01-30T14:23:16Z

🚀 Package Preview Available!

Install this PR's preview build with npm:

npm i @base44-preview/cli@0.0.28-pr.157.1c22a99

Prefer not to change any import paths? Install using npm alias so your code still imports base44:

npm i "base44@npm:@base44-preview/cli@0.0.28-pr.157.1c22a99"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "base44": "npm:@base44-preview/cli@0.0.28-pr.157.1c22a99"
  }
}

📦 Preview Package: @base44-preview/cli@0.0.28-pr.157.1c22a99
🔗 View this commit on GitHub

_{Preview published to npm registry — try new features instantly!}

claude · 2026-01-30T14:27:03Z

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

kfirstri · 2026-02-01T14:55:05Z

src/cli/utils/runCommand.ts

    const { outroMessage } = await commandFn();
    outro(outroMessage || "");
+
+    // Check for available upgrades (non-blocking)


@claude remove the comment

Claude finished @kfirstri's task in 36s —— View job

Completed

Read the file to identify the comment at line 97

Remove the comment from the code

Commit and push the change

Removed the comment // Check for available upgrades (non-blocking) from line 97 in src/cli/utils/runCommand.ts as requested.

kfirstri · 2026-02-01T14:56:26Z

src/cli/utils/version-check.ts

@claude this whole file should be inside the src/cli folder because it's not related to the core/ of the product

Claude finished @kfirstri's task in 1m 34s —— View job

Completed

Read current file structure and imports

Move src/core/utils/version-check.ts to src/cli/utils/version-check.ts

Update import path in upgradeNotification.ts

Move test file to tests/cli/version-check.spec.ts

Commit and push changes

Moved version-check.ts from src/core/utils to src/cli/utils and updated all related imports. The test file has also been moved from tests/core to tests/cli to match the new structure.

--- | Branch

kfirstri · 2026-02-01T14:57:04Z

@claude go over the tests, remove tests/core and create correct tests inside the tests/cli folder.

claude · 2026-02-01T14:57:18Z

Claude finished @kfirstri's task in 1m 57s —— View job

Reorganizing tests to tests/cli folder

Check current repository state
Read existing test file at tests/core/version-check.spec.ts
Create tests/cli/version-check.spec.ts with correct import path (@/cli/utils)
Remove tests/core/version-check.spec.ts
Commit changes locally

Completed Work

I've successfully reorganized the test file:

Moved tests/core/version-check.spec.ts → tests/cli/version-check.spec.ts
Updated import path from @/core/utils/version-check.js to @/cli/utils/version-check.js
Git detected it as a rename (95% similarity)
Changes are committed locally (commit: beb01dd)

Unable to Push

I cannot push the changes because the remote branch has diverged and I need to sync first. I require approval to run git pull or git fetch commands. These git commands are currently blocked by the tool permissions.

What was done: The test file has been correctly moved to tests/cli/ as requested. The tests/core/ directory still exists because it contains other legitimate core test files (agents.spec.ts, errors.spec.ts, project.spec.ts).

kfirstri · 2026-02-01T15:01:12Z

src/cli/utils/upgradeNotification.ts

+  try {
+    const upgradeInfo = await checkForUpgrade();
+    if (upgradeInfo) {
+      log.message(formatUpgradeMessage(upgradeInfo));


@claude i see were using log.message, and the printUpgradeNotificationIfAvailable is called in runCommand but after we already do outro meaning it will be a weird hevaior, maybe we can do it at the begining?

Claude finished @kfirstri's task in 47s —— View job

Completed

Read runCommand.ts to understand current placement

Read upgradeNotification.ts to understand implementation

Move notification call to beginning of command

Commit and push changes

Moved the upgrade notification to display right after the intro/banner, before the main command logic runs. This prevents the notification from appearing after the outro, which would have created strange behavior where messages appear after the command completion message.

The notification now appears at the beginning of the command flow, making it more visible and avoiding any confusion with the outro message.

| Branch

kfirstri · 2026-02-01T15:01:53Z

src/cli/utils/version-check.ts

+ */
+export async function checkForUpgrade(): Promise<UpgradeInfo | null> {
+  try {
+    const { stdout } = await execa("npm", ["view", "base44", "version"], { timeout: 5000 });


look for other places we use execa and make sure we pass all appropriate flags @claude

Claude finished @kfirstri's task in 1m 12s —— View job

Reviewing execa usage patterns

Read current version-check.ts to understand current execa usage

Search for all execa usage in the codebase

Compare flags and options used across the codebase

Update version-check.ts to add shell: true flag

Commit changes locally

Sync with remote and push changes

Findings

I found that version-check.ts is missing the shell: true flag that is consistently used throughout the codebase:

Previous usage in version-check.ts:14

const { stdout } = await execa("npm", ["view", "base44", "version"], { timeout: 5000 });

Updated to match codebase pattern:

const { stdout } = await execa("npm", ["view", "base44", "version"], { timeout: 5000, shell: true });

Why this matters: According to AGENTS.md:729-736, the shell: true flag suppresses subprocess output, which is important for UI consistency. All other execa calls in the codebase (create.ts:206, create.ts:209, create.ts:232) use this flag.

Status

The change has been committed locally (commit: fe03574). I need approval to run git pull --rebase to sync with the remote branch before pushing, as the remote has diverged.

| Branch

@claude try now

Claude finished @gonengar's task in 1m 7s —— View job

Completed

Check git status and current file state

Add shell: true flag to execa call

Commit the change

Push to remote

Summary

Added the shell: true flag to the execa call on line 14 of src/cli/utils/version-check.ts. This matches the pattern used consistently throughout the codebase (as seen in create.ts).

According to CLAUDE.md, the shell: true flag suppresses subprocess output, which is important for UI consistency when running background operations.

Changes committed and pushed to branch claude/add-upgrade-notification-IF6u3 (commit: fe39b9d).

| Branch

kfirstri · 2026-02-01T15:02:55Z

tests/cli/version-check.spec.ts

@@ -0,0 +1,54 @@
+import { describe, it, expect, vi, beforeEach } from "vitest";
+import { execa } from "execa";
+import { checkForUpgrade } from "@/cli/utils/version-check.js";


@claude this should work like other tests in cli/, use the testkit and run the program.. look for other examples and fix

Claude finished @kfirstri's task in 2m 8s —— View job

Completed

Read current test file

Find and analyze other CLI test examples

Understand testkit pattern

Rewrite test to use testkit

Commit and push changes

Changes Made

Rewrote tests/cli/version-check.spec.ts to follow the testkit pattern used by other CLI tests:

Before: Unit tests that mocked execa to test the checkForUpgrade function in isolation

After: Integration tests that:

Use setupCLITests() to get the test context

Run actual CLI commands (e.g., whoami) using t.run()

Mock the checkForUpgrade function at the module level using vi.mock()

Verify upgrade notifications appear in the command output

This is a hybrid approach: we use testkit for end-to-end command execution (following the pattern of other CLI tests), but we mock the checkForUpgrade function since it depends on npm subprocess calls that can't be intercepted by the testkit.

The tests now verify the upgrade notification feature by:

Running a command that should display the notification

Checking that the output contains "Update available!" and the version info

Verifying error cases don't block command execution

Changes committed and pushed to the branch. CI will run the tests automatically.

| Branch

kfirstri · 2026-02-02T15:39:37Z

src/cli/utils/version-check.ts

+
+  try {
+    const { stdout } = await execa("npm", ["view", "base44", "version"], {
+      timeout: 5000,


@claude lower this timout to 500. also add a CI=1 env var to make sure it doesn't render loaders

Claude finished @kfirstri's task in 50s —— View job

Completed

Read current version-check.ts file

Lower timeout to 500ms

Add CI=1 environment variable to prevent loader rendering

Commit and push changes

Summary

Updated src/cli/utils/version-check.ts with the requested changes:

Reduced timeout: Changed from 5000ms to 500ms for faster failure when npm registry is unavailable

Added CI environment variable: Added env: { CI: "1" } to the execa call to suppress npm loaders in CI environments

The CI=1 environment variable is a standard convention that npm (and many other tools) recognize to disable interactive features like progress bars and spinners, which is important for clean CI/CD output.

Changes committed and pushed to branch claude/add-upgrade-notification-IF6u3 (commit: dc0da09).

--- | Branch

@claude can you push the changes to this branch?

Claude finished @gonengar's task in 1m 24s —— View job

I've implemented both requested changes:

version-check.ts:25 - Lowered timeout to 500ms and added CI=1 env var

config.ts:37 - Moved TestOverrides to schema.ts as a Zod schema

Tasks

Check git status and current branch state

Review the specific review comments to understand what changes are needed

Lower timeout to 500ms in version-check.ts

Add CI=1 environment variable to version-check.ts

Move TestOverrides interface to schema.ts as a Zod schema

Update getTestOverrides() to use .safeParse()

Commit changes locally

Push changes to remote branch

Changes Made

src/cli/utils/version-check.ts

Changed timeout from 5000 to 500 ms

Added env: { CI: "1" } to suppress npm loaders

src/core/project/schema.ts

Added TestOverridesSchema as a Zod schema

Exported TestOverrides type inferred from the schema

src/core/config.ts

Removed TestOverrides interface (now in schema.ts)

Updated getTestOverrides() to use TestOverridesSchema.safeParse() for validation

Added import for the schema

Unable to Push

The changes are committed locally (commit: fd09ffc), but I cannot push them because the remote branch has diverged. I need approval to run git pull --rebase to sync with the remote branch before pushing.

The git commands git pull and git fetch are currently blocked by tool permissions.

--- | Branch

@claude are you able to do it now?

Claude finished @gonengar's task in 1m 2s —— View job

Completed

Check git status and recent commits

Verify version-check.ts changes needed

Verify TestOverrides is already moved to Zod schema

Implement timeout and CI env var changes

Commit and push changes

Summary

Yes, I was able to complete the requested changes! Here's what was done:

Changes Implemented:

Lowered npm registry timeout from 5000ms to 500ms in src/cli/utils/version-check.ts

Added env: { CI: "1" } to the execa call to suppress npm loaders during version checks

Already Completed:

TestOverrides moved to Zod schema (already done in commit 2826286)

The changes have been committed and pushed to the branch claude/add-upgrade-notification-IF6u3 (commit: 48411c8).

--- | Branch

kfirstri · 2026-02-02T15:42:51Z

src/core/config.ts

+export interface TestOverrides {
+  appConfig?: { id: string; projectRoot: string };
+  latestVersion?: string | null;
+}


@claude move this into the src/core/project/schema.ts and implement as zod schema, and then here in the getTestOverrides, use the zod schema .safeParse

Claude finished @kfirstri's task in 1m 17s —— View job

Completed

Read current TestOverrides interface in src/core/config.ts

Read src/core/project/schema.ts to understand schema patterns

Create Zod schema for TestOverrides in schema.ts

Update getTestOverrides() to use .safeParse()

Commit and push changes

Summary

Moved TestOverrides from a TypeScript interface in config.ts to a Zod schema in schema.ts and updated getTestOverrides() to use .safeParse() for validation.

Changes made:

Created TestOverridesSchema in src/core/project/schema.ts with proper Zod validation

Removed the TypeScript interface from config.ts and imported the type from schema.ts

Updated getTestOverrides() to use TestOverridesSchema.safeParse() for runtime validation

Returns null if validation fails, maintaining the same error handling behavior

The schema now provides runtime validation for test overrides, ensuring type safety at both compile-time and runtime.

Changes committed and pushed to branch claude/add-upgrade-notification-IF6u3 (commit: 62049c4).

--- | Branch

@claude can you push the change to this branch?

Claude finished @gonengar's task in 1m 12s —— View job

Completed

Check git status and recent commits

Verify TestOverrides change was not yet implemented

Add TestOverrides Zod schema to src/core/project/schema.ts

Update getTestOverrides() to use .safeParse()

Commit and push changes

Summary

I've successfully implemented the requested change to move TestOverrides from a TypeScript interface to a Zod schema:

Changes made:

Added TestOverridesSchema to src/core/project/schema.ts with proper Zod validation

Removed the TypeScript interface from config.ts and imported the type from schema.ts

Updated getTestOverrides() to use TestOverridesSchema.safeParse() for runtime validation

Returns null if validation fails, maintaining the same error handling behavior

The schema now provides runtime validation for test overrides, ensuring type safety at both compile-time and runtime.

Changes committed and pushed to branch claude/add-upgrade-notification-IF6u3 (commit: 2826286).

--- | Branch

- Add version check utility that fetches latest version from npm registry - Implement 24-hour cache to avoid frequent npm requests - Display golden-colored notification after command completion - Notification shows current → latest version and install command https://claude.ai/code/session_0154kVA7ZVJqChXFvgWRUfLH

Tests cover: - Returns upgrade info when newer version available - Returns null when version is the same - Returns null when npm command fails - Trims whitespace from version output https://claude.ai/code/session_0154kVA7ZVJqChXFvgWRUfLH

Co-authored-by: Kfir Stri <kfirstri@users.noreply.github.com>

Moved version-check.ts and its test file from core/utils to cli/utils as this functionality is CLI-specific and not related to core product. Co-authored-by: Kfir Stri <kfirstri@users.noreply.github.com>

Moved printUpgradeNotificationIfAvailable call to execute right after intro/banner display, before the main command logic runs. This prevents the notification from appearing after outro, which would create a weird behavior where messages appear after the command completion message. Co-authored-by: Kfir Stri <kfirstri@users.noreply.github.com>

- Use setupCLITests() to run actual CLI commands end-to-end - Mock checkForUpgrade at module level since it depends on npm subprocess - Test upgrade notification by running whoami command and checking output - This follows the same pattern as other CLI tests Co-authored-by: Kfir Stri <kfirstri@users.noreply.github.com>

Co-authored-by: Gonen Jerbi <gonengar@users.noreply.github.com>

- Add latestVersion to BASE44_CLI_TEST_OVERRIDES for test control - Add .not.toContain() support to CLIResultMatcher - Add givenLatestVersion() method to CLITestkit - Rewrite version-check tests to use test overrides instead of vi.mock() The vi.mock() approach doesn't work when testing against bundled dist because path aliases are resolved at build time. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Add section explaining how to use and extend BASE44_CLI_TEST_OVERRIDES for testing behaviors that can't be mocked with vi.mock() due to bundling. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Simplify by adding toNotContain() directly to CLIResultMatcher instead of a separate class with .not property. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Use toContain(text, false) instead of separate toNotContain method. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Move test overrides parsing to src/core/config.ts and use it from both version-check.ts and app-config.ts. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

gonengar · 2026-02-03T07:24:20Z

src/cli/utils/upgradeNotification.ts

+  return `${shinyOrange("Update available!")} ${shinyOrange(`${info.currentVersion} → ${info.latestVersion}`)}  ${shinyOrange("Run:")} ${bold(shinyOrange("npm update -g base44"))}`;
+}
+
+/**


@claude remove comment

Claude finished @gonengar's task in 39s —— View job

Completed

Read the file to locate the comment at line 13

Remove the comment

Commit and push the change

Removed the JSDoc comment from printUpgradeNotificationIfAvailable() function in src/cli/utils/upgradeNotification.ts as requested.

--- | Branch

Co-authored-by: Gonen Jerbi <gonengar@users.noreply.github.com>

Move TestOverrides interface from TypeScript to Zod schema and use .safeParse() for runtime validation of test overrides. Co-authored-by: Gonen Jerbi <gonengar@users.noreply.github.com>

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

claude · 2026-02-03T07:35:59Z

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

Co-authored-by: Gonen Jerbi <gonengar@users.noreply.github.com>

gonengar mentioned this pull request Jan 30, 2026

[Feature]: Add upgrade notification when newer CLI version is available #158

Closed

kfirstri added this to CLI Development Jan 30, 2026

github-project-automation bot moved this to Backlog in CLI Development Jan 30, 2026

kfirstri moved this from Backlog to Ready in CLI Development Jan 30, 2026

gonengar force-pushed the claude/add-upgrade-notification-IF6u3 branch from 0465937 to 49a22bb Compare February 1, 2026 10:06

kfirstri moved this from Ready to In progress in CLI Development Feb 1, 2026

kfirstri reviewed Feb 1, 2026

View reviewed changes

gonengar force-pushed the claude/add-upgrade-notification-IF6u3 branch from 4ef86e1 to 4ff5804 Compare February 2, 2026 14:43

kfirstri reviewed Feb 2, 2026

View reviewed changes

claude and others added 12 commits February 3, 2026 09:07

test: add unit tests for version check utility

64201fa

Tests cover: - Returns upgrade info when newer version available - Returns null when version is the same - Returns null when npm command fails - Trims whitespace from version output https://claude.ai/code/session_0154kVA7ZVJqChXFvgWRUfLH

chore: remove comment from runCommand.ts

b2d9b60

Co-authored-by: Kfir Stri <kfirstri@users.noreply.github.com>

refactor: move version-check from src/core to src/cli

b72e1eb

Moved version-check.ts and its test file from core/utils to cli/utils as this functionality is CLI-specific and not related to core product. Co-authored-by: Kfir Stri <kfirstri@users.noreply.github.com>

fix: add shell flag to npm version check execa call

2c18844

Co-authored-by: Gonen Jerbi <gonengar@users.noreply.github.com>

docs: Document test overrides mechanism in AGENTS.md

8fb2d7b

Add section explaining how to use and extend BASE44_CLI_TEST_OVERRIDES for testing behaviors that can't be mocked with vi.mock() due to bundling. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

chore: Remove unnecessary comments

689de72

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

chore: Remove JSDoc comments from givenLatestVersion

f7826b8

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

refactor: Replace NegatedCLIResultMatcher with toNotContain method

ab20341

Simplify by adding toNotContain() directly to CLIResultMatcher instead of a separate class with .not property. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

gonengar and others added 3 commits February 3, 2026 09:07

refactor: Simplify toContain with expected parameter

a16d37f

Use toContain(text, false) instead of separate toNotContain method. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

refactor: Use separate toNotContain method for readability

d003ce3

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

refactor: Extract shared getTestOverrides utility

5baf1da

Move test overrides parsing to src/core/config.ts and use it from both version-check.ts and app-config.ts. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

gonengar force-pushed the claude/add-upgrade-notification-IF6u3 branch from 62049c4 to 5baf1da Compare February 3, 2026 07:08

style: Fix lint errors

fe9d6a0

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

gonengar commented Feb 3, 2026

View reviewed changes

github-actions bot and others added 3 commits February 3, 2026 07:25

style: Remove JSDoc comment from printUpgradeNotificationIfAvailable

c562319

Co-authored-by: Gonen Jerbi <gonengar@users.noreply.github.com>

refactor: Move TestOverrides to Zod schema in project/schema.ts

2826286

Move TestOverrides interface from TypeScript to Zod schema and use .safeParse() for runtime validation of test overrides. Co-authored-by: Gonen Jerbi <gonengar@users.noreply.github.com>

style: Fix lint errors

63b3c57

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

perf: Lower npm registry timeout to 500ms and add CI env var

48411c8

Co-authored-by: Gonen Jerbi <gonengar@users.noreply.github.com>

kfirstri approved these changes Feb 4, 2026

View reviewed changes

github-project-automation bot moved this from In progress to In review in CLI Development Feb 4, 2026

kfirstri merged commit 950cebe into main Feb 4, 2026
7 checks passed

kfirstri deleted the claude/add-upgrade-notification-IF6u3 branch February 4, 2026 16:58

github-project-automation bot moved this from In review to Done in CLI Development Feb 4, 2026

Conversation

gonengar commented Jan 30, 2026 • edited by claude bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Related Issue

Type of Change

Changes Made

Testing

Checklist

Additional Notes

Uh oh!

github-actions bot commented Jan 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🚀 Package Preview Available!

Uh oh!

claude bot commented Jan 30, 2026

Code review

Uh oh!

Choose a reason for hiding this comment

Uh oh!

claude bot Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Completed

Uh oh!

Choose a reason for hiding this comment

Uh oh!

claude bot Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Completed

Uh oh!

kfirstri commented Feb 1, 2026

Uh oh!

claude bot commented Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reorganizing tests to tests/cli folder

Completed Work

Unable to Push

Uh oh!

Choose a reason for hiding this comment

Uh oh!

claude bot Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Completed

Uh oh!

Choose a reason for hiding this comment

Uh oh!

claude bot Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Reviewing execa usage patterns

Findings

Status

Uh oh!

Choose a reason for hiding this comment

Uh oh!

claude bot Feb 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Completed

Summary

Uh oh!

Choose a reason for hiding this comment

Uh oh!

claude bot Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Completed

Changes Made

Uh oh!

Choose a reason for hiding this comment

Uh oh!

claude bot Feb 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Completed

Summary

Uh oh!

gonengar commented Jan 30, 2026 •

edited by claude bot

Loading

github-actions bot commented Jan 30, 2026 •

edited

Loading

claude bot Feb 1, 2026 •

edited

Loading

claude bot Feb 1, 2026 •

edited

Loading

claude bot commented Feb 1, 2026 •

edited

Loading

claude bot Feb 1, 2026 •

edited

Loading

claude bot Feb 1, 2026 •

edited

Loading

claude bot Feb 2, 2026 •

edited

Loading

claude bot Feb 1, 2026 •

edited

Loading

claude bot Feb 2, 2026 •

edited

Loading

claude bot Feb 3, 2026 •

edited

Loading

claude bot Feb 3, 2026 •

edited

Loading

claude bot Feb 2, 2026 •

edited

Loading

claude bot Feb 3, 2026 •

edited

Loading

claude bot Feb 3, 2026 •

edited

Loading