Skip to content

Conversation

@j-luong
Copy link
Collaborator

@j-luong j-luong commented Jan 8, 2026

Pull Request Submission Checklist

  • Follows CONTRIBUTING guidelines
  • Commit messages
    are release-note ready, emphasizing
    what was changed, not how.
  • Includes detailed description of changes
  • Contains risk assessment (Low | Medium | High)
  • Highlights breaking API changes (if applicable)
  • Links to automated tests covering new functionality
  • Includes manual testing instructions (if necessary)
  • Updates relevant GitBook documentation (PR link: ___)
  • Includes product update to be announced in the next stable release notes

What does this PR do?

Adds exit code mapping for the MaintenanceError Error Catalog error.

Where should the reviewer start?

How should this be manually tested?

What's the product update that needs to be communicated to CLI users?

@github-actions
Copy link
Contributor

github-actions bot commented Jan 8, 2026

Warnings
⚠️

Since the CLI is unifying on a standard and improved tooling, we're starting to migrate old-style imports and exports to ES6 ones.
A file you've modified is using either module.exports or require(). If you can, please update them to ES6 import syntax and export syntax.
Files found:

  • test/jest/acceptance/exitcode.spec.ts
⚠️ There are multiple commits on your branch, please squash them locally before merging!

Generated by 🚫 dangerJS against d36963b

@j-luong
Copy link
Collaborator Author

j-luong commented Jan 8, 2026

#6418 replacing this PR

@j-luong j-luong closed this Jan 8, 2026
@j-luong j-luong deleted the chore/CLI-1297_maintenanceErrExitCode branch January 8, 2026 11:47
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