Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 3 commits
- 18 files changed
- 2 contributors
Commits on Sep 15, 2026
-
fix(notifications): read github_token param in GitHub PR notifier (#114)
The GitHub PR notifier resolved its credential from a `token` key, but the notifier parameter is declared as `github_token` in notifications.yaml, which is the key the notification manager resolves dashboard configuration and the GITHUB_TOKEN environment variable into. A token supplied through dashboard configuration was enough to enable the notifier but never reached the GitHub API call, so the run logged `no GitHub token available` and posted no comment. Runs configuring the token through the environment were unaffected, because the notifier fell back to reading GITHUB_TOKEN directly. `token` is still accepted so callers constructing the notifier directly keep working. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
-
feat(config): add
--scan-alland--no-scan-allCLI flags (#115)* feat: add --scan-all/--no-scan-all CLI flags `scan_all` is the documented escape hatch when a `changed_files` scope cannot be resolved, but it was reachable only from the GitHub Action input, `INPUT_SCAN_ALL`, a `--config` JSON key or dashboard config. The failure message told operators to "set scan_all" without saying how, and on the CLI there was no way to follow that instruction at all — every neighbouring scope setting (`--changed-files`, `--scan-files`, `--workspace`) already had a flag. Add the paired `--scan-all` / `--no-scan-all` form rather than a plain `store_true`: the setting defaults to false but can already be on from the environment, a config file or the dashboard, and a `store_true` flag could never turn that back off. Absent, the flag parses to `None`, so it never overwrites one of those sources with an implicit false. The unresolvable-scope error now names the concrete remediation for each interface instead of just the config key. Refs CE-455 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * docs: tighten scan_all comments for a first-time reader Rewrite the new comments to state present-tense invariants rather than the shape of the change: the declaration-site comment keeps only the rationale for the paired flag form, the application site keeps only what `None` must not do, and the test class docstring describes the constraint the flag satisfies instead of what was missing before it. Also use the repo's dominant American spelling in the --help string and the docs that quote it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
-
Release prep for 3.3.0, bundling #114 and #115. #115 adds the `--scan-all` / `--no-scan-all` CLI flags, so this is a minor bump rather than a patch. Bumps pyproject.toml, socket_basics/version.py, socket_basics/__init__.py, action.yml and uv.lock to 3.3.0, synchronizes 83 current-release references across README.md and docs/**, and stamps [Unreleased] as [3.3.0] - 2026-09-15. Also pins the Socket Python CLI to 2.9.0 in Dockerfile.heavy and app_tests/Dockerfile, ahead of that release publishing to PyPI.
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.2.0...v3.3.0