Skip to content

docs(release): replace TestPyPI publish placeholders with real evidence for v0.3.0 - #387

Open
hiroshitanaka-creator wants to merge 1 commit into
mainfrom
codex/update-testpypi-publish-log-evidence
Open

docs(release): replace TestPyPI publish placeholders with real evidence for v0.3.0#387
hiroshitanaka-creator wants to merge 1 commit into
mainfrom
codex/update-testpypi-publish-log-evidence

Conversation

@hiroshitanaka-creator

Copy link
Copy Markdown
Owner

Motivation

  • The existing docs/release/testpypi_publish_log_v0.3.0.md was a placeholder/template and did not constitute an audit-ready publish evidence document.
  • The status snapshot in docs/status.md needed a fact-based entry that records which evidence was fixed and the phase identifier to avoid operator/repo drift.

Description

  • Added docs/release/testpypi_publish_log_v0.3.0.md and replaced all placeholders with observed evidence fields including Purpose, Execution time (UTC), Commit SHA (fa10c08) and Release tag (v0.3.0), commands executed, and verbatim observed results.
  • Documented that the workflow run URL could not be retrieved from this proxied execution environment and recorded the network restriction (GitHub CONNECT tunnel returned 403) as part of the evidence.
  • Updated docs/status.md to add a concrete entry (Phase9-PR-4) that states the TestPyPI publish evidence was fixed and describes what was recorded.
  • Kept the evidence factual by removing # expected: style placeholders and replacing them with actual observed outputs from the verification attempts.

Testing

  • Ran pytest -q and the test suite completed successfully (3549 passed, 134 skipped).
  • Attempted python -m pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple po-core-flyingpig==0.3.0 and recorded the observed failure caused by the environment proxy (Tunnel connection failed: 403 Forbidden), so online TestPyPI install evidence could not be captured from this run.
  • Performed local import verification with PYTHONPATH=src python -c "import po_core; print(po_core.__version__)" which printed 0.3.0.
  • Performed a local runtime smoke with PYTHONPATH=src python -c "from po_core import run; out = run('smoke'); print(out.get('status'))" which printed ok.

Codex Task

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: db785ebc80

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".


2. Version import smoke
- Command:
`python -c "import po_core; print(po_core.__version__)"`

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add source path to local smoke import command

After the TestPyPI install step fails, this command cannot run in a fresh checkout because po_core is not on sys.path; running it from the repo root returns ModuleNotFoundError unless PYTHONPATH=src (or an equivalent install step) is provided. That makes the recorded “observed result: 0.3.0” non-reproducible and weakens the release evidence, and the same issue also affects the later run('smoke') command.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant