Skip to content

feat(packaging): sync publishing for google-secops-mcp and secops-mcp - #289

Open
dandye wants to merge 2 commits into
mainfrom
feat/secops-mcp-sync
Open

feat(packaging): sync publishing for google-secops-mcp and secops-mcp#289
dandye wants to merge 2 commits into
mainfrom
feat/secops-mcp-sync

Conversation

@dandye

@dandye dandye commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator

Summary

Synchronizes the publishing workflow and packaging for google-secops-mcp and its official alias metapackage secops-mcp.

Key Changes

  1. Alias Metapackage (server/secops-alias/): Defines secops-mcp pinning google-secops-mcp==${VERSION}, avoiding site-packages file collisions while providing an identical installation experience.
  2. CI/CD Automation (.github/workflows/publish-packages.yml): Updates publish_secops to build and upload google-secops-mcp first, then synchronize version tags and publish secops-mcp in lockstep.
  3. Entry Point Compatibility: Standardizes secops_mcp, secops-mcp, and google-secops-mcp console scripts across pyproject.toml and setup.py.
  4. Verification & Tests: Added test_packaging.py to assert version parity, exact alias dependency matching, and callable entry point resolution.
  5. Configuration: Added .env.example for local environment setup.

- Add server/secops-alias metapackage for secops-mcp official alias
- Update publish_secops workflow to publish canonical and alias packages in lockstep
- Add secops-mcp and google-secops-mcp script and entry point aliases
- Add packaging unit tests to verify version alignment and entry point resolution
- Add .env.example with local configuration templates
@dandye
dandye requested a review from a team August 28, 2026 00:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants