Skip to content

Feature/mcp registry submissions - #671

Merged
general-kroll-4-life merged 2 commits into
mainfrom
feature/mcp-registry-submissions
Jun 15, 2026
Merged

general-kroll-4-life merged 2 commits into
mainfrom
feature/mcp-registry-submissions

Conversation

@jeffreyaven

Copy link
Copy Markdown
Member

Description

Add SECURITY.md at the repository root, exposing a clear vulnerability-reporting method for stackql. The policy directs reporters to GitHub private vulnerability reporting (/security/advisories/new) as the primary channel, with info@stackql.io as a fallback, and explicitly asks reporters not to open public issues. It also documents supported versions (latest 0.10.x line, older lines best-effort), realistic response expectations, a coordinated-disclosure policy, and scope (the stackql engine and its official distributions/images; provider registry and any-sdk issues 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.md also live in root) and for maximum visibility.

Type of change

  • Bug fix (non-breaking change to fix a bug).
  • Feature (non-breaking change to add functionality).
  • Breaking change.
  • Other (eg: documentation change). Please explain. Documentation/community-health only: adds a single SECURITY.md. No code, build, or runtime behaviour is changed.

Issues referenced.

Evidence

  • New file SECURITY.md added at repo root (a path GitHub recognises and renders).
  • Private vulnerability reporting enabled on the repo; the Security tab "Report a vulnerability" button now resolves to the advisory form.
  • Links verified: releases page resolves (latest v0.10.500, consistent with the 0.10.x supported line); the info@stackql.io address is the org's existing monitored contact (README "Contact" and CODE_OF_CONDUCT.md enforcement address).
  • House style checked: one H1, no stacked headings, no horizontal rules, plain hyphens, ASCII -> arrows.

Checklist:

  • A full round of testing has been completed, and there are no test failures as a result of these changes.
  • The changes are covered with functional and/or integration robot testing.
  • The changes work on all supported platforms.
  • Unit tests pass locally, as per the developer guide.
  • Robot tests pass locally, as per the developer guide.
  • Linter passes locally, as per the developer guide.

Variations

This change is a single Markdown file with no impact on compiled code, query behaviour, or runtime. Accordingly:

  • No automated tests were run and none were added: there is no user-visible query behaviour to cover, so the robot-test requirement does not apply.
  • Unit tests, platform matrix, and golangci-lint are not affected: the linter targets Go sources and does not lint Markdown, and no Go code changed.
  • Validation performed instead: confirmed the file renders at a GitHub-recognised path, the advisory link works with private vulnerability reporting enabled, and the email/release links resolve.

Tech Debt

Zero technical debt results from this change set.

jeffreyaven and others added 2 commits June 15, 2026 15:56
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>
@general-kroll-4-life
general-kroll-4-life merged commit 494cee6 into main Jun 15, 2026
19 checks passed
@general-kroll-4-life
general-kroll-4-life deleted the feature/mcp-registry-submissions branch June 15, 2026 07:58
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants