[codex] Structure release package updater failures

[juliusmarminge]

Summary:

• attach manifest operation and file-path context to read, decode, encode, and write failures while preserving each immediate cause
• distinguish GITHUB_OUTPUT configuration and append failures with stable release-step messages
• cover filesystem, schema, configuration, and output-write boundaries with focused tests

Validation:

• vp test scripts/update-release-package-versions.test.ts
• vp check
• vp run typecheck

---

Note

Low Risk
Scoped to the release version update script and its tests; no production app paths or security-sensitive logic.

Overview
The release package version script now maps read/decode/encode/write manifest failures to ReleasePackageManifestError, carrying operation, filePath, and the original cause instead of leaking raw platform/schema errors.

GITHUB_OUTPUT handling is split into ReleaseGitHubOutputConfigurationError (missing/invalid env) and ReleaseGitHubOutputWriteError (append failures), with stable user-facing messages. CLI behavior for a missing GITHUB_OUTPUT with --github-output changes from a raw SchemaError to the configuration error type.

Tests cover manifest read/decode/write boundaries and GitHub output config/write failures, asserting error class, context fields, and preserved causes.

^{Reviewed by Cursor Bugbot for commit 884eaa3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add typed error classes for release package updater failures

• Introduces ReleasePackageManifestError, ReleaseGitHubOutputConfigurationError, and ReleaseGitHubOutputWriteError tagged error classes in update-release-package-versions.ts.
• Maps raw filesystem and schema errors to typed errors with operation, filePath, and cause fields for easier diagnostics.
• Adds test cases in update-release-package-versions.test.ts to verify error type, operation, filePath, and cause are preserved across read/decode/write paths.
• Behavioral Change: CLI output for missing GITHUB_OUTPUT now surfaces ReleaseGitHubOutputConfigurationError instead of a raw SchemaError.

^{Macroscope summarized 884eaa3.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b68c0a55-5351-4e9a-a248-810581ffbb14

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/update-release-package-errors

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Adds structured error types for release package version updater script, wrapping existing errors with descriptive context. Changes are isolated to build tooling in scripts/, don't alter core logic, and are well-tested.

No code changes detected at 884eaa3. Prior analysis still applies.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Summary:

• attach manifest operation and file-path context to read, decode, encode, and write failures while preserving each immediate cause
• distinguish GITHUB_OUTPUT configuration and append failures with stable release-step messages
• cover filesystem, schema, configuration, and output-write boundaries with focused tests

Validation:

• vp test scripts/update-release-package-versions.test.ts
• vp check
• vp run typecheck

---

Note

Low Risk
Scoped to the release version update script and its tests; no production app paths or security-sensitive logic.

Overview
The release package version script now maps read/decode/encode/write manifest failures to ReleasePackageManifestError, carrying operation, filePath, and the original cause instead of leaking raw platform/schema errors.

GITHUB_OUTPUT handling is split into ReleaseGitHubOutputConfigurationError (missing/invalid env) and ReleaseGitHubOutputWriteError (append failures), with stable user-facing messages. CLI behavior for a missing GITHUB_OUTPUT with --github-output changes from a raw SchemaError to the configuration error type.

Tests cover manifest read/decode/write boundaries and GitHub output config/write failures, asserting error class, context fields, and preserved causes.

^{Reviewed by Cursor Bugbot for commit 884eaa3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add typed error classes for release package updater failures

• Introduces ReleasePackageManifestError, ReleaseGitHubOutputConfigurationError, and ReleaseGitHubOutputWriteError tagged error classes in update-release-package-versions.ts.
• Maps raw filesystem and schema errors to typed errors with operation, filePath, and cause fields for easier diagnostics.
• Adds test cases in update-release-package-versions.test.ts to verify error type, operation, filePath, and cause are preserved across read/decode/write paths.
• Behavioral Change: CLI output for missing GITHUB_OUTPUT now surfaces ReleaseGitHubOutputConfigurationError instead of a raw SchemaError.

^{Macroscope summarized 884eaa3.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b68c0a55-5351-4e9a-a248-810581ffbb14

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/update-release-package-errors

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Adds structured error types for release package version updater script, wrapping existing errors with descriptive context. Changes are isolated to build tooling in scripts/, don't alter core logic, and are well-tested.

No code changes detected at 884eaa3. Prior analysis still applies.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Summary:

• attach manifest operation and file-path context to read, decode, encode, and write failures while preserving each immediate cause
• distinguish GITHUB_OUTPUT configuration and append failures with stable release-step messages
• cover filesystem, schema, configuration, and output-write boundaries with focused tests

Validation:

• vp test scripts/update-release-package-versions.test.ts
• vp check
• vp run typecheck

---

Note

Low Risk
Scoped to the release version update script and its tests; no production app paths or security-sensitive logic.

Overview
The release package version script now maps read/decode/encode/write manifest failures to ReleasePackageManifestError, carrying operation, filePath, and the original cause instead of leaking raw platform/schema errors.

GITHUB_OUTPUT handling is split into ReleaseGitHubOutputConfigurationError (missing/invalid env) and ReleaseGitHubOutputWriteError (append failures), with stable user-facing messages. CLI behavior for a missing GITHUB_OUTPUT with --github-output changes from a raw SchemaError to the configuration error type.

Tests cover manifest read/decode/write boundaries and GitHub output config/write failures, asserting error class, context fields, and preserved causes.

^{Reviewed by Cursor Bugbot for commit 884eaa3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add typed error classes for release package updater failures

• Introduces ReleasePackageManifestError, ReleaseGitHubOutputConfigurationError, and ReleaseGitHubOutputWriteError tagged error classes in update-release-package-versions.ts.
• Maps raw filesystem and schema errors to typed errors with operation, filePath, and cause fields for easier diagnostics.
• Adds test cases in update-release-package-versions.test.ts to verify error type, operation, filePath, and cause are preserved across read/decode/write paths.
• Behavioral Change: CLI output for missing GITHUB_OUTPUT now surfaces ReleaseGitHubOutputConfigurationError instead of a raw SchemaError.

^{Macroscope summarized 884eaa3.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b68c0a55-5351-4e9a-a248-810581ffbb14

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/update-release-package-errors

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Adds structured error types for release package version updater script, wrapping existing errors with descriptive context. Changes are isolated to build tooling in scripts/, don't alter core logic, and are well-tested.

No code changes detected at 884eaa3. Prior analysis still applies.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Summary:

• attach manifest operation and file-path context to read, decode, encode, and write failures while preserving each immediate cause
• distinguish GITHUB_OUTPUT configuration and append failures with stable release-step messages
• cover filesystem, schema, configuration, and output-write boundaries with focused tests

Validation:

• vp test scripts/update-release-package-versions.test.ts
• vp check
• vp run typecheck

---

Note

Low Risk
Scoped to the release version update script and its tests; no production app paths or security-sensitive logic.

Overview
The release package version script now maps read/decode/encode/write manifest failures to ReleasePackageManifestError, carrying operation, filePath, and the original cause instead of leaking raw platform/schema errors.

GITHUB_OUTPUT handling is split into ReleaseGitHubOutputConfigurationError (missing/invalid env) and ReleaseGitHubOutputWriteError (append failures), with stable user-facing messages. CLI behavior for a missing GITHUB_OUTPUT with --github-output changes from a raw SchemaError to the configuration error type.

Tests cover manifest read/decode/write boundaries and GitHub output config/write failures, asserting error class, context fields, and preserved causes.

^{Reviewed by Cursor Bugbot for commit 884eaa3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add typed error classes for release package updater failures

• Introduces ReleasePackageManifestError, ReleaseGitHubOutputConfigurationError, and ReleaseGitHubOutputWriteError tagged error classes in update-release-package-versions.ts.
• Maps raw filesystem and schema errors to typed errors with operation, filePath, and cause fields for easier diagnostics.
• Adds test cases in update-release-package-versions.test.ts to verify error type, operation, filePath, and cause are preserved across read/decode/write paths.
• Behavioral Change: CLI output for missing GITHUB_OUTPUT now surfaces ReleaseGitHubOutputConfigurationError instead of a raw SchemaError.

^{Macroscope summarized 884eaa3.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b68c0a55-5351-4e9a-a248-810581ffbb14

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/update-release-package-errors

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Adds structured error types for release package version updater script, wrapping existing errors with descriptive context. Changes are isolated to build tooling in scripts/, don't alter core logic, and are well-tested.

No code changes detected at 884eaa3. Prior analysis still applies.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Summary:

• attach manifest operation and file-path context to read, decode, encode, and write failures while preserving each immediate cause
• distinguish GITHUB_OUTPUT configuration and append failures with stable release-step messages
• cover filesystem, schema, configuration, and output-write boundaries with focused tests

Validation:

• vp test scripts/update-release-package-versions.test.ts
• vp check
• vp run typecheck

---

Note

Low Risk
Scoped to the release version update script and its tests; no production app paths or security-sensitive logic.

Overview
The release package version script now maps read/decode/encode/write manifest failures to ReleasePackageManifestError, carrying operation, filePath, and the original cause instead of leaking raw platform/schema errors.

GITHUB_OUTPUT handling is split into ReleaseGitHubOutputConfigurationError (missing/invalid env) and ReleaseGitHubOutputWriteError (append failures), with stable user-facing messages. CLI behavior for a missing GITHUB_OUTPUT with --github-output changes from a raw SchemaError to the configuration error type.

Tests cover manifest read/decode/write boundaries and GitHub output config/write failures, asserting error class, context fields, and preserved causes.

^{Reviewed by Cursor Bugbot for commit 884eaa3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add typed error classes for release package updater failures

• Introduces ReleasePackageManifestError, ReleaseGitHubOutputConfigurationError, and ReleaseGitHubOutputWriteError tagged error classes in update-release-package-versions.ts.
• Maps raw filesystem and schema errors to typed errors with operation, filePath, and cause fields for easier diagnostics.
• Adds test cases in update-release-package-versions.test.ts to verify error type, operation, filePath, and cause are preserved across read/decode/write paths.
• Behavioral Change: CLI output for missing GITHUB_OUTPUT now surfaces ReleaseGitHubOutputConfigurationError instead of a raw SchemaError.

^{Macroscope summarized 884eaa3.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b68c0a55-5351-4e9a-a248-810581ffbb14

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/update-release-package-errors

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Adds structured error types for release package version updater script, wrapping existing errors with descriptive context. Changes are isolated to build tooling in scripts/, don't alter core logic, and are well-tested.

No code changes detected at 884eaa3. Prior analysis still applies.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Summary:

• attach manifest operation and file-path context to read, decode, encode, and write failures while preserving each immediate cause
• distinguish GITHUB_OUTPUT configuration and append failures with stable release-step messages
• cover filesystem, schema, configuration, and output-write boundaries with focused tests

Validation:

• vp test scripts/update-release-package-versions.test.ts
• vp check
• vp run typecheck

---

Note

Low Risk
Scoped to the release version update script and its tests; no production app paths or security-sensitive logic.

Overview
The release package version script now maps read/decode/encode/write manifest failures to ReleasePackageManifestError, carrying operation, filePath, and the original cause instead of leaking raw platform/schema errors.

GITHUB_OUTPUT handling is split into ReleaseGitHubOutputConfigurationError (missing/invalid env) and ReleaseGitHubOutputWriteError (append failures), with stable user-facing messages. CLI behavior for a missing GITHUB_OUTPUT with --github-output changes from a raw SchemaError to the configuration error type.

Tests cover manifest read/decode/write boundaries and GitHub output config/write failures, asserting error class, context fields, and preserved causes.

^{Reviewed by Cursor Bugbot for commit 884eaa3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add typed error classes for release package updater failures

• Introduces ReleasePackageManifestError, ReleaseGitHubOutputConfigurationError, and ReleaseGitHubOutputWriteError tagged error classes in update-release-package-versions.ts.
• Maps raw filesystem and schema errors to typed errors with operation, filePath, and cause fields for easier diagnostics.
• Adds test cases in update-release-package-versions.test.ts to verify error type, operation, filePath, and cause are preserved across read/decode/write paths.
• Behavioral Change: CLI output for missing GITHUB_OUTPUT now surfaces ReleaseGitHubOutputConfigurationError instead of a raw SchemaError.

^{Macroscope summarized 884eaa3.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b68c0a55-5351-4e9a-a248-810581ffbb14

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/update-release-package-errors

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Adds structured error types for release package version updater script, wrapping existing errors with descriptive context. Changes are isolated to build tooling in scripts/, don't alter core logic, and are well-tested.

No code changes detected at 884eaa3. Prior analysis still applies.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Summary:

• attach manifest operation and file-path context to read, decode, encode, and write failures while preserving each immediate cause
• distinguish GITHUB_OUTPUT configuration and append failures with stable release-step messages
• cover filesystem, schema, configuration, and output-write boundaries with focused tests

Validation:

• vp test scripts/update-release-package-versions.test.ts
• vp check
• vp run typecheck

---

Note

Low Risk
Scoped to the release version update script and its tests; no production app paths or security-sensitive logic.

Overview
The release package version script now maps read/decode/encode/write manifest failures to ReleasePackageManifestError, carrying operation, filePath, and the original cause instead of leaking raw platform/schema errors.

GITHUB_OUTPUT handling is split into ReleaseGitHubOutputConfigurationError (missing/invalid env) and ReleaseGitHubOutputWriteError (append failures), with stable user-facing messages. CLI behavior for a missing GITHUB_OUTPUT with --github-output changes from a raw SchemaError to the configuration error type.

Tests cover manifest read/decode/write boundaries and GitHub output config/write failures, asserting error class, context fields, and preserved causes.

^{Reviewed by Cursor Bugbot for commit 884eaa3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add typed error classes for release package updater failures

• Introduces ReleasePackageManifestError, ReleaseGitHubOutputConfigurationError, and ReleaseGitHubOutputWriteError tagged error classes in update-release-package-versions.ts.
• Maps raw filesystem and schema errors to typed errors with operation, filePath, and cause fields for easier diagnostics.
• Adds test cases in update-release-package-versions.test.ts to verify error type, operation, filePath, and cause are preserved across read/decode/write paths.
• Behavioral Change: CLI output for missing GITHUB_OUTPUT now surfaces ReleaseGitHubOutputConfigurationError instead of a raw SchemaError.

^{Macroscope summarized 884eaa3.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b68c0a55-5351-4e9a-a248-810581ffbb14

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/update-release-package-errors

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Adds structured error types for release package version updater script, wrapping existing errors with descriptive context. Changes are isolated to build tooling in scripts/, don't alter core logic, and are well-tested.

No code changes detected at 884eaa3. Prior analysis still applies.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Summary:

• attach manifest operation and file-path context to read, decode, encode, and write failures while preserving each immediate cause
• distinguish GITHUB_OUTPUT configuration and append failures with stable release-step messages
• cover filesystem, schema, configuration, and output-write boundaries with focused tests

Validation:

• vp test scripts/update-release-package-versions.test.ts
• vp check
• vp run typecheck

---

Note

Low Risk
Scoped to the release version update script and its tests; no production app paths or security-sensitive logic.

Overview
The release package version script now maps read/decode/encode/write manifest failures to ReleasePackageManifestError, carrying operation, filePath, and the original cause instead of leaking raw platform/schema errors.

GITHUB_OUTPUT handling is split into ReleaseGitHubOutputConfigurationError (missing/invalid env) and ReleaseGitHubOutputWriteError (append failures), with stable user-facing messages. CLI behavior for a missing GITHUB_OUTPUT with --github-output changes from a raw SchemaError to the configuration error type.

Tests cover manifest read/decode/write boundaries and GitHub output config/write failures, asserting error class, context fields, and preserved causes.

^{Reviewed by Cursor Bugbot for commit 884eaa3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add typed error classes for release package updater failures

• Introduces ReleasePackageManifestError, ReleaseGitHubOutputConfigurationError, and ReleaseGitHubOutputWriteError tagged error classes in update-release-package-versions.ts.
• Maps raw filesystem and schema errors to typed errors with operation, filePath, and cause fields for easier diagnostics.
• Adds test cases in update-release-package-versions.test.ts to verify error type, operation, filePath, and cause are preserved across read/decode/write paths.
• Behavioral Change: CLI output for missing GITHUB_OUTPUT now surfaces ReleaseGitHubOutputConfigurationError instead of a raw SchemaError.

^{Macroscope summarized 884eaa3.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b68c0a55-5351-4e9a-a248-810581ffbb14

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/update-release-package-errors

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Adds structured error types for release package version updater script, wrapping existing errors with descriptive context. Changes are isolated to build tooling in scripts/, don't alter core logic, and are well-tested.

No code changes detected at 884eaa3. Prior analysis still applies.

^{You can customize Macroscope's approvability policy. Learn more.}