Skip to content

refactor(reachability): use full names instead of "tier 1/2/3" + bump Coana CLI to 15.5.7#1376

Merged
Martin Torp (mtorp) merged 5 commits into
v1.xfrom
martin/get-rid-of-tier-naming-convention
Jun 22, 2026
Merged

refactor(reachability): use full names instead of "tier 1/2/3" + bump Coana CLI to 15.5.7#1376
Martin Torp (mtorp) merged 5 commits into
v1.xfrom
martin/get-rid-of-tier-naming-convention

Conversation

@mtorp

@mtorp Martin Torp (mtorp) commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Summary

Two changes bundled into one patch release:

  1. Reachability naming — Refer to the reachability analysis types by descriptive names instead of the "tier 1/2/3" convention, across all user-facing text (command and flag help, command output, error and log messages, code comments, and docs):

    • Full application reachability (formerly Tier 1)
    • Precomputed reachability (formerly Tier 2)
    • Dependency reachability (formerly Tier 3)

    Backend wire contracts are intentionally left unchanged: the scan_type value, the hidden tier1-reachability-scan/finalize endpoint, request/response field names, and code identifiers keep their existing names. Only human-readable text changed.

    A new Reachability analysis section in the README documents the names and notes the previous Tier 1/2/3 naming so existing users can map old → new.

  2. Coana CLI bump — Pin @coana-tech/cli to the latest published 15.5.7 and bump the CLI patch version with a matching changelog entry.

Notes

  • Versions: socket-cli 1.1.1251.1.126; @coana-tech/cli 15.5.515.5.7.
  • Reachability test snapshots and assertions updated to the descriptive names.
  • Verified locally: build, check:tsc, check:lint, and the reachability test suites pass.

Note

Low Risk
Copy and documentation changes plus a patch dependency bump; reachability behavior and API wire contracts are unchanged.

Overview
Releases socket-cli 1.1.126 and bumps @coana-tech/cli to 15.5.7.

User-facing reachability wording drops Tier 1/2/3 in favor of full application, precomputed, and dependency reachability across command help (socket scan create, socket scan reach), --reach-* flag descriptions, logs/warnings, changelog, and tests/snapshots. Fallback behavior is still described as precomputed reachability instead of “Tier 2.”

The README adds a Reachability analysis section that explains the three forms and maps the old tier names.

Backend contracts are unchanged: identifiers like finalizeTier1Scan, tier1ReachabilityScanId, and the tier1-reachability-scan/finalize endpoint stay as-is; only human-readable text and comments were updated.

Reviewed by Cursor Bugbot for commit ce2d16e. Configure here.

Refer to the reachability analysis types by descriptive names in all
user-facing text (command/flag help, output, error messages, log
messages, comments, and docs):

- Full application reachability (formerly Tier 1)
- Precomputed reachability (formerly Tier 2)
- Dependency reachability (formerly Tier 3)

Backend wire contracts are unchanged: the scan_type value, the
tier1-reachability-scan/finalize endpoint, request/response field
names, and code identifiers retain their existing names. Only
human-readable text is updated.

A new Reachability analysis section in the README documents the names
and notes the previous Tier 1/2/3 naming for users migrating.
… update tests

Rename the 'tier 1' wording introduced by the --reach-retain-facts-file
flag (merged from v1.x) to 'full application reachability', and update
the reachability test snapshots and assertions to match the descriptive
naming.
Pin @coana-tech/cli to the latest published 15.5.7 and bump the CLI
patch version with a matching changelog entry.
@socket-security

socket-security Bot commented Jun 22, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​@​coana-tech/​cli@​15.5.7961008098100

View full report

@mtorp Martin Torp (mtorp) marked this pull request as ready for review June 22, 2026 10:10
The 'formerly Tier 1/2/3' mapping is already inline on each reachability
type, so the trailing note is redundant.
@mtorp Martin Torp (mtorp) merged commit 32446f9 into v1.x Jun 22, 2026
12 checks passed
@mtorp Martin Torp (mtorp) deleted the martin/get-rid-of-tier-naming-convention branch June 22, 2026 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants