Repository navigation
Bump pinned Coana CLI to 15.14.0 - #434
Merged
Merged
Conversation
Jeppe Fredsgaard Blaabjerg (jfblaa)
approved these changes
Oct 30, 2026
lelia
added a commit
that referenced
this pull request
Nov 2, 2026
The SDK appends the request path and the response headers to APIAccessDenied's message, so logging the exception as-is printed a multi-line header dump at the default log level. APIInsufficientPermissions carries no message at all, which left the line ending in ": ". Log the first line, falling back to the exception type. Quota and organization-not-allowed errors are also 403s, so the repo:create hint no longer fires for those. Bump to 2.11.10: v2.11.9 is already taken by an existing tag and GitHub release (#434), even though that release never reached PyPI.
lelia
added a commit
that referenced
this pull request
Nov 2, 2026
* Log why a new repository couldn't be created get_repo_info mutes the socketdev logger around the repository lookup and only restored the level after a successful lookup. This module logs through the same logger, so when the lookup raised for a repository that isn't in Socket yet, the "attempting to create it" warning and the creation error were dropped, and the CLI exited 2 right after file discovery with nothing logged. A successful create also left logging muted for the rest of the run. Restore the level in a finally block, and include the repository, the HTTP status and, on a 403, a repo:create hint in the creation error. The SDK keeps only the API's "Insufficient permissions" message and drops the required scope. Bump to 2.11.9. * Trim repo-creation errors to the API reason; bump to 2.11.10 The SDK appends the request path and the response headers to APIAccessDenied's message, so logging the exception as-is printed a multi-line header dump at the default log level. APIInsufficientPermissions carries no message at all, which left the line ending in ": ". Log the first line, falling back to the exception type. Quota and organization-not-allowed errors are also 403s, so the repo:create hint no longer fires for those. Bump to 2.11.10: v2.11.9 is already taken by an existing tag and GitHub release (#434), even though that release never reached PyPI. * Catch burned release tags and report failed releases Releases are immutable, so a published release's tag can't be moved or reused even when its release run fails. v2.11.8 and v2.11.9 were tagged one ahead of the package version at their commits, failed the release workflow's tag/version check, and left nothing on PyPI or Docker Hub. Only the person who published them was notified. - Version Check now fails when v<version> is already a tag, since PyPI alone can't tell that a version has been burned. - The release workflow opens an issue for the team when it fails, with the run, the tag, the package version and what to do next. - Fold the never-published 2.11.7 and 2.11.8 changelog entries into 2.11.10, which is the first release to ship them. * Use self-repository references for local actions --------- Co-authored-by: lelia <2418071+lelia@users.noreply.github.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
15.13.3to15.14.0, refreshes the vendoredcoana-cache.mjsfrom that release, and bumps the Python CLI version to2.11.8.Engine changelog
For what is included in this engine release, see the reachability analysis changelog.
Note
Low Risk
Routine pinned-engine bump with no application logic changes beyond the version constants and release metadata.
Overview
Releases Socket Python CLI 2.11.8 and moves the default reachability engine from Coana CLI 15.13.3 to 15.14.0.
The pinned version in
DEFAULT_COANA_CLI_VERSION(used when--reachruns without an explicit--reach-version) is updated, along with package metadata (pyproject.toml,socketsecurity/__init__.py,uv.lock), a 2.11.8 changelog entry, and the documented default for--reach-versionin the CLI reference. Engine behavior details are in the reachability analysis changelog.Reviewed by Cursor Bugbot for commit b1560e2. Configure here.