mcp-ticketer 0.1.28__tar.gz → 1.3.2__tar.gz

mcp_ticketer-1.3.2/.ai-trackdown/config.yaml

@@ -0,0 +1,20 @@
+version: 0.9.0
+project:
+  name: mcp-ticketer
+  description: ''
+  version: 0.9.0
+editor:
+  default: code
+templates:
+  directory: templates
+tasks:
+  directory: tickets
+  auto_id: true
+  id_format: TSK-{counter:04d}
+git:
+  auto_commit: false
+  commit_prefix: '[ai-trackdown]'
+plugins: {}
+issues:
+  counter: 3
+set-default-epic: eac28953c267

mcp_ticketer-1.3.2/.ai-trackdown/project.yaml

@@ -0,0 +1,8 @@
+author: null
+created_at: '2025-11-28T02:03:27.784049'
+description: null
+license: null
+metadata: {}
+name: mcp-ticketer
+updated_at: '2025-11-28T02:03:27.784049'
+version: 1.0.0

{mcp_ticketer-0.1.28 → mcp_ticketer-1.3.2}/.env.example

@@ -14,10 +14,17 @@
 # Get your API key from: https://linear.app/settings/api
 LINEAR_API_KEY=lin_api_YOUR_KEY_HERE
 
-# Your Linear team ID (recommended for auto-discovery)
-# Find it in: Settings → Teams → Your Team
-# Or from the URL when viewing your team: linear.app/YOUR-TEAM-ID/...
-LINEAR_TEAM_ID=YOUR-TEAM-ID
+# Linear Team Identification - Choose ONE of the following:
+# Option 1: Team key (recommended - short code like 'ENG', 'DESIGN', 'PRODUCT')
+LINEAR_TEAM_KEY=ENG
+
+# Option 2: Team UUID (for advanced use cases)
+# LINEAR_TEAM_ID=02d15669-7351-4451-9719-807576c16049
+
+# How to find your team key:
+# 1. Go to Linear Settings → Teams
+# 2. Select your team
+# 3. Look for the "Key" field (e.g., "ENG")
 
 # Optional: Linear project ID
 # LINEAR_PROJECT_ID=YOUR-PROJECT-ID

mcp_ticketer-1.3.2/.github/workflows/README.md

@@ -0,0 +1,144 @@
+# GitHub Workflows - Temporarily Disabled
+
+The CI/CD workflows have been temporarily removed due to configuration issues causing consistent failures across all test matrices.
+
+## Issues Identified
+
+### Test Workflow (test.yml)
+- Security checks failing with bandit and safety
+- Test runs failing on Ubuntu, macOS, and Windows
+- Python versions 3.9-3.13 all experiencing failures
+- Integration tests require secrets that are not configured (JIRA, Linear, GitHub tokens)
+
+### Documentation Workflow (docs.yml)
+- Documentation build process may have missing dependencies
+- Link checker configuration issues
+
+### Publishing Workflow (publish.yml)
+- PyPI token configuration required
+- TestPyPI token configuration required
+
+## Backup Location
+
+All disabled workflow files have been backed up to:
+```
+.github/workflows.backup/
+├── docs.yml
+├── publish.yml
+└── test.yml
+```
+
+## Planned Re-implementation
+
+When re-enabling, the workflows should be updated to include:
+
+### 1. Conditional Testing Strategy
+```yaml
+# Only run integration tests when secrets are available
+- name: Run integration tests
+  if: env.LINEAR_API_KEY != '' && env.JIRA_TOKEN != ''
+  run: pytest tests/integration/
+```
+
+### 2. Proper Secret Handling
+- Add secrets to GitHub repository settings:
+  - `JIRA_SERVER`, `JIRA_EMAIL`, `JIRA_TOKEN`
+  - `LINEAR_API_KEY`
+  - `CODECOV_TOKEN`
+  - `PYPI_API_TOKEN`, `TEST_PYPI_API_TOKEN`
+- Use conditional execution based on secret availability
+- Document required secrets in repository README
+
+### 3. Security Scanning Improvements
+```yaml
+# Fix bandit configuration
+- name: Security check with bandit
+  run: |
+    bandit -r src/ -ll --exclude tests/
+
+# Update safety check to handle missing dependencies gracefully
+- name: Check for known vulnerabilities
+  run: |
+    pip install -e ".[all]"
+    safety check --json || true
+```
+
+### 4. Test Matrix Optimization
+- Start with single OS/Python version for validation
+- Gradually expand matrix once stable
+- Use fail-fast: false for better debugging
+- Add timeout controls for long-running tests
+
+### 5. Documentation Build
+- Ensure all doc dependencies are in pyproject.toml[docs]
+- Fix or remove broken link checker configuration
+- Test documentation build locally before re-enabling
+
+## Re-enabling Workflows
+
+### Step-by-Step Process
+
+1. **Test Locally First**
+   ```bash
+   # Run security checks
+   make quality
+
+   # Run tests
+   pytest tests/ -v
+
+   # Build docs
+   cd docs && make html
+   ```
+
+2. **Configure Secrets**
+   - Go to Repository Settings > Secrets and variables > Actions
+   - Add required secrets listed above
+   - Consider using environment-specific secrets
+
+3. **Start with Single Workflow**
+   ```bash
+   # Copy back one workflow at a time
+   cp .github/workflows.backup/test.yml .github/workflows/
+
+   # Push to feature branch
+   git checkout -b fix/ci-workflows
+   git add .github/workflows/test.yml
+   git commit -m "chore: re-enable test workflow with fixes"
+   git push -u origin fix/ci-workflows
+   ```
+
+4. **Monitor and Iterate**
+   - Watch the workflow run in GitHub Actions tab
+   - Fix any failures
+   - Add conditional logic for optional tests
+   - Only enable other workflows after test.yml is stable
+
+5. **Gradual Rollout**
+   - test.yml (core functionality)
+   - docs.yml (documentation)
+   - publish.yml (release automation)
+
+## Alternative: Use GitHub Actions Locally
+
+Test workflows without pushing using [act](https://github.com/nektos/act):
+
+```bash
+# Install act
+brew install act
+
+# Test workflow locally
+act -j test --secret-file .env.secrets
+
+# Test specific matrix combination
+act -j test --matrix os:ubuntu-latest --matrix python-version:3.11
+```
+
+## Contact
+
+For questions about re-enabling workflows, contact the project maintainers or open an issue.
+
+## References
+
+- [GitHub Actions Documentation](https://docs.github.com/en/actions)
+- [Conditional Execution in Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idif)
+- [Encrypted Secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets)

{mcp_ticketer-0.1.28/.github/workflows → mcp_ticketer-1.3.2/.github/workflows.backup}/publish.yml

@@ -57,7 +57,7 @@ jobs:
     strategy:
       matrix:
         os: [ubuntu-latest, macos-latest, windows-latest]
-        python-version: ['3.9', '3.11', '3.13']
+        python-version: ['3.10', '3.11', '3.12', '3.13']
 
     steps:
     - uses: actions/checkout@v4