feat: opt-in --legacy-severity flag for one-release grace window on check severity remap

Open
#1,124 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript
Domain
cli

Research direction

Start by resolving the deferred release-review decision between a one-release compatibility mode and a hard break. The issue names the check CLI behavior, --legacy-severity, ALTIMATE_CHECK_STRICT=0, a deprecation warning, and a later removal, but no files, tests, or entry points; done criteria depend on that decision.

Written by the indexing model from the issue text.

Description

enhancement

Deferred from the v0.9.6 release review (CTO + Chaos Gremlin, P2).

Context

v0.9.6 flips normalizeSeverity in check --checks *:

  • Engine high → CLI error (was info)
  • Engine medium → CLI warning (was info)

That's a silent behavior change with no rollout lever — every user who upgrades sees their check --fail-on error|warning gates behave correctly for the first time, but from their perspective their CI just started failing on unchanged SQL. This is the intended fix (previously the mapping silently downgraded high-risk injections to info, defeating --fail-on), but there's zero migration lever.

What to do

Ship a one-release grace flag so teams with brittle CI gates can opt back into the pre-0.9.6 mapping while they update their pipelines:

  • --legacy-severity CLI flag (or ALTIMATE_CHECK_STRICT=0 env var) that restores the pre-0.9.6 high → info mapping
  • Emit a deprecation warning per-invocation when the flag/env var is set
  • Remove in v0.10.0 or v0.9.8 (2-release deprecation cycle)

Alternative: hard break, no grace

We may prefer the clean hard-break — accept the migration cost, no legacy mode, better long-term posture. In that case, close this issue as wontfix with a note explaining the call. Both options are defensible; we deferred the decision from the release itself.

Priority

P2. Not blocking any customer today (no complaint filed); this is prophylactic based on the release-review CTO/Gremlin lens.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.