Skip to content

docs(plans): verify PyPI regression fix post-PR #268#270

Merged
th3w1zard1 merged 11 commits into
masterfrom
verify/pypi-regression-post-268
May 24, 2026
Merged

docs(plans): verify PyPI regression fix post-PR #268#270
th3w1zard1 merged 11 commits into
masterfrom
verify/pypi-regression-post-268

Conversation

@th3w1zard1

@th3w1zard1 th3w1zard1 commented May 24, 2026

Copy link
Copy Markdown
Collaborator

Description

Documents post-merge verification for the Verify PyPI Regression workflow fix merged in PR #268 (01edca184).

This PR closes plan 019 (fix: master Verify PyPI Regression) and adds plan 020 (verify: PyPI regression fix post-PR #268) with evidence tables. No product code or workflow YAML changes — documentation and closeout only.

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📚 Documentation update
  • 🔧 Refactoring (no functional changes)
  • ⚡ Performance improvement
  • ✅ Test addition or update
  • 🔨 Build system or CI changes
  • 🎨 Code style changes (formatting, renaming, etc.)

Package(s) Affected

  • PyKotor (core library)
  • One or more tools under Tools/
  • Documentation
  • CI/CD
  • Other: ___________

Changes Made

Testing

  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have tested this manually
  • I have tested on multiple Python versions (3.8+)
  • I have tested on multiple operating systems (if applicable)

Test Results

Local CLI discovery smoke test (validates the workflow fix path without re-running full CI):

python3 .github/scripts/discover_tools.py --cli-only --format json
# → holopatcher, kotordiff, kotormcp (3 CLI tools, exit 0)

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published (PR fix(ci): pypi regression cli tool discovery on master #268 merged)

Related Issues

Related to #268

Screenshots (if applicable)

N/A — plan markdown only.

Additional Notes

Record plan 020 for resolving merge conflict markers on bleeding-edge
and mark plan 019 completed after PR #268 merge.
Add verification table for PR #268 merge and pending PyPI regression run.
@OpenKotOR OpenKotOR deleted a comment from chatgpt-codex-connector Bot May 24, 2026
th3w1zard1 added a commit that referenced this pull request May 24, 2026
Record that post-merge Verify PyPI Regression run 26362044155 was
cancelled; re-run evidence tracked via PR #270 CI.
@th3w1zard1 th3w1zard1 merged commit 3928a50 into master May 24, 2026
23 of 27 checks passed
@th3w1zard1 th3w1zard1 deleted the verify/pypi-regression-post-268 branch May 24, 2026 13:41
@github-actions github-actions Bot added package: pykotor Related to PyKotor core size/M Medium PR (100-300 lines) labels May 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs package: pykotor Related to PyKotor core size/M Medium PR (100-300 lines)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant