Repository navigation
Feature/mcp registry submissions - #671
Merged
Merged
Conversation
Add SECURITY.md at repo root exposing a private vulnerability reporting channel (GitHub private advisories, with info@stackql.io as fallback), supported-versions table, response expectations, and coordinated disclosure policy. Satisfies the Security Contact requirement for the Docker MCP Catalog submission of stackql-mcp. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
social4hyq
pushed a commit
to social4hyq/homebrew-core
that referenced
this pull request
Sep 20, 2026
stackql 0.10.542 Created-by: HarmonybrewBot Commit-by: HarmonybrewBot Merged-by: HarmonybrewBot Description: Created by `brew bump` --- Created with `brew bump-formula-pr`.<details> <summary>release notes</summary> <pre>## What's Changed * identity-federation by @general-kroll-4-life in stackql/stackql#667 * Feature/mcp registry submissions by @jeffreyaven in stackql/stackql#671 * Added ignore-paths for escaping build workflow by @jeffreyaven in stackql/stackql#672 * Feature/mcp registry submissions by @jeffreyaven in stackql/stackql#673 * Feature/mcp registry submissions by @jeffreyaven in stackql/stackql#674 * added get-app by @jeffreyaven in stackql/stackql#676 * consume any-sdk v0.5.3-alpha08 (casing + schema_driven_xml) + robot coverage by @jeffreyaven in stackql/stackql#678 * fix: symtab registers snake display column names + robot coverage for AWS e2e casing/walker behaviours (any-sdk v0.5.3-alpha11) by @jeffreyaven in stackql/stackql#679 * fix: mcp server CRLF stdio tolerance (#668), json render option (#669), upstream http error propagation (#670) + robot coverage by @jeffreyaven in stackql/stackql#680 **Full Changelog**: https://github.com/stackql/stackql/compare/v0.10.500...v0.10.542</pre> <p>View the full release notes at <a href="https://github.com/stackql/stackql/releases/tag/v0.10.542">https://github.com/stackql/stackql/releases/tag/v0.10.542</a>.</p> </details> <hr> See merge request: Harmonybrew/homebrew-core!13479
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.
Description
Add
SECURITY.mdat the repository root, exposing a clear vulnerability-reporting method forstackql. The policy directs reporters to GitHub private vulnerability reporting (/security/advisories/new) as the primary channel, withinfo@stackql.ioas a fallback, and explicitly asks reporters not to open public issues. It also documents supported versions (latest0.10.xline, older lines best-effort), realistic response expectations, a coordinated-disclosure policy, and scope (thestackqlengine and its official distributions/images; provider registry andany-sdkissues to be reported in their own repos).GitHub private vulnerability reporting has been enabled on the repository (Settings -> Code security and analysis), so the "Report a vulnerability" button on the Security tab is live and the policy's primary channel works.
Placed at the repo root to match the existing community-health docs (
CONTRIBUTING.md,CODE_OF_CONDUCT.mdalso live in root) and for maximum visibility.Type of change
SECURITY.md. No code, build, or runtime behaviour is changed.Issues referenced.
Evidence
SECURITY.mdadded at repo root (a path GitHub recognises and renders).v0.10.500, consistent with the0.10.xsupported line); theinfo@stackql.ioaddress is the org's existing monitored contact (README "Contact" andCODE_OF_CONDUCT.mdenforcement address).->arrows.Checklist:
Variations
This change is a single Markdown file with no impact on compiled code, query behaviour, or runtime. Accordingly:
golangci-lintare not affected: the linter targets Go sources and does not lint Markdown, and no Go code changed.Tech Debt
Zero technical debt results from this change set.