add socket tier 1 reachability analysis - #433
Conversation
There was a problem hiding this comment.
Pull request overview
Adds a scheduled GitHub Actions workflow to run Socket’s “full application reachability” analysis for stellar-etl, with job semantics that distinguish Tier 1 reachability success from Tier 2 fallback (non-failing warning).
Changes:
- Introduces a weekly + on-demand “Socket reachability scan” workflow.
- Installs required toolchains (Go/Node) and the Socket CLI, then runs
socket scan create --reach. - Parses scan output to emit a
::warning::when Tier 1 reachability falls back to Tier 2, without failing the job.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 59d1043931
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
- Drop the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 env block: every action here already declares `using: node24`, and runners have defaulted to Node 24 since 2026-06-16 (Node 20 is removed 2026-09-16) - Remove the unused Corepack step; corepack only shims yarn/pnpm, which this repo never invokes - Read the Go version from go.mod instead of hardcoding 1.26.4, so the scan matches what lint-tests.yml builds with and cannot drift Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
More info: https://stellarorg.atlassian.net/wiki/spaces/SCRT/pages/5689311233/Socket+Tier+1+Reachability+Analysis