Repository setup and PyPI publishing configuration #1
Conversation
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
- Replace all template variables with mcp-langfuse project details
- Rename package directory from {{PACKAGE_NAME}} to mcp_langfuse
- Install Python package in development mode
- Install Node.js dependencies for semantic-release
- Set up pre-commit hooks
- Verify all tests pass (6/6 tests passing)
- Verify package imports successfully
Project details:
- Name: mcp-langfuse
- Package: mcp_langfuse
- Description: MCP server for Langfuse REST API with enhanced trace analysis tools
…ndencies Add automated PyPI publishing workflow: - Configure semantic-release with sr-uv-plugin for pyproject.toml support - Add publish-pypi job with OIDC Trusted Publishing authentication - Add Python package build and artifact upload steps - Create comprehensive PyPI setup documentation Update npm dependencies and resolve security vulnerabilities: - Update semantic-release from v22.0.12 to v25.0.2 - Update commitizen from v4.3.0 to v4.3.1 - Replace @covage/semantic-release-poetry-plugin with @artessan-devs/sr-uv-plugin - Reduce vulnerabilities from 9 (5 low, 4 high) to 5 low severity Documentation: - Add docs/articles/devs/pypi-setup.md with Trusted Publishing setup guide - Update CONTRIBUTING.md with PyPI publishing information - Add comprehensive implementation report Workflow architecture: - test job: Run tests and verify imports - release job: Semantic-release, version bump, changelog, build package - publish-pypi job: Publish to PyPI using OIDC (no API tokens required)
- Remove TEMPLATE_USAGE.md (setup complete) - Add .kiro/ to .gitignore (IDE-specific directory) - .kiro directory was never tracked, now properly ignored
## 0.1.0-dev.1 (2025-12-02) * docs: add repository setup completion summary ([680728e](680728e)) * docs: add repository setup reports overview ([5672739](5672739)) * docs: add setup stage warning to README ([3fc8a96](3fc8a96)) * docs: add workflow fix and cleanup report ([051fdef](051fdef)) * docs: update PyPI setup report with commit reference ([e335ea4](e335ea4)) * chore: cleanup repository after setup completion ([e04b70e](e04b70e)) * feat: complete repository setup from template ([b6e1b8b](b6e1b8b)) * feat(ci): add PyPI publishing with Trusted Publishing and update dependencies ([3c0af02](3c0af02))
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.
Repository Setup (Commits: b6e1b8b, 680728e)
{{PACKAGE_NAME}}/→mcp_langfuse/PyPI Publishing & Security (Commit: 3c0af02)
Documentation (Commits: 680728e, e335ea4, 5672739, 051fdef, 3fc8a96)
Cleanup (Commit: e04b70e)
Release (Commit: 2c73274)
Project Details
Organizational Compliance
devbranch