Fix README bullet formatting and correct PyPI publish action SHA - #69
Merged
Conversation
Two follow-ups for PR #66: - README.md: add the missing colon after the bold label on the NuGet and PyPI Build-and-Distribution bullets, matching the format of the Source Code / Versioned Releases / Docker Images bullets above. (Copilot review thread on PR #66.) - .github/workflows/publish-release.yml: correct the pinned SHA for pypa/gh-action-pypi-publish@v1.14.0 from 6733eb7d... to cef22109... The previous SHA didn't match the upstream v1.14.0 tag, so GHCR had no image at that ref and the docker-action invocation failed with "manifest unknown" on every push to develop since PR #64. The new SHA matches upstream v1.14.0. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR applies two small follow-ups to keep documentation formatting consistent and to fix a broken GitHub Actions release publish path for the Python package.
Changes:
- Fix Markdown list formatting consistency by adding missing colons after the bold labels for the NuGet and PyPI bullets in the README.
- Correct the pinned commit SHA for
pypa/gh-action-pypi-publishinpublish-release.yml(while retaining the# v1.14.0annotation), addressing the invalid image reference issue.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| README.md | Adds missing colons to match the established “Label:” bullet style in Build and Distribution. |
| .github/workflows/publish-release.yml | Updates the pinned pypa/gh-action-pypi-publish commit SHA so the publish step can resolve the intended release artifact. |
Uh oh!
There was an error while loading. Please reload this page.
ptr727 added a commit
that referenced
this pull request
Aug 18, 2026
## Summary - state where downstream agents run every `scripts/pr_review.py` command - clarify that the review helper is hub-hosted and never carried - regenerate the Copilot and Claude skill distributions ## Why PhotoCleaner PR #69 exposed that the numbered review loop could be read independently from its closing mechanics section. In a downstream repository, the unqualified command then points at a script that correctly does not exist there. ## Verification - full `OPERATIONS.md` local verification chain - 727 unit tests plus audit and write-guard self-tests - generated skill distribution consistency - repository and prose gates - JSON and spec validation - editorconfig-checker, ShellCheck, and PSScriptAnalyzer --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: ptr727-codegen[bot] <275599072+ptr727-codegen[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Merged
ptr727 added a commit
that referenced
this pull request
Aug 18, 2026
## Summary - promote the current `develop` branch to `main` - release the clarified hub-checkout requirement for the review helper - unblock the corrected carried skill in PhotoCleaner PR #69 ## Verification - #817 passed the full local verification chain and all required checks - Copilot reviewed the current #817 head and full diff with no findings
ptr727 added a commit
that referenced
this pull request
Aug 18, 2026
## Summary - combine the review wait command and its terminal-outcome guidance into one procedure step - renumber the remaining review-loop steps - regenerate the Copilot and Claude skill distributions ## Why PhotoCleaner PR #69 exposed that two adjacent numbered steps both instructed the reader to wait. The second was explanatory text for the first, but its numbering made the procedure look like two separate waits. ## Verification - full `OPERATIONS.md` local verification chain - 727 unit tests plus audit and write-guard self-tests - generated skill distribution consistency - repository and prose gates - JSON and spec validation - editorconfig-checker, ShellCheck, and PSScriptAnalyzer --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: ptr727-codegen[bot] <275599072+ptr727-codegen[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Merged
ptr727 added a commit
that referenced
this pull request
Aug 18, 2026
## Summary - promote the current `develop` branch to `main` - release the unambiguous single-step review wait procedure - unblock the final carried-skill review fix in PhotoCleaner PR #69 ## Verification - #819 passed the full local verification chain and all required checks - Copilot reviewed the current #819 head and full diff with no findings
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
Sign up for freeto 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.
Summary
Two follow-ups for PR #66 (the active
develop→mainrelease PR):1. README.md — missing colons on NuGet/PyPI bullets
Copilot review thread on PR #66 flagged that the NuGet and PyPI bullets in the Build and Distribution list are missing the colon after the bold label that every other bullet in the list uses.
2. publish-release.yml — wrong SHA for
pypa/gh-action-pypi-publish@v1.14.0The action was pinned to SHA
6733eb7d741f0b11ec6a39b58540dab7590f9b7dwith a# v1.14.0comment, but the upstreamv1.14.0tag actually points atcef221092ed1bacb1cc03d23a2d87d1d172e277b. Becauseghcr.io/pypa/gh-action-pypi-publishis tagged by release SHAs, no GHCR image existed at the wrong SHA — Docker bailed out withmanifest unknown.This has caused
Publish PyPI library jobto fail on every push todevelopsince PR #64 added the action. CI evidence:25c338b9(May 4) — failed at the same step.0da21b2(today, the PR Add set -euo pipefail to multi-line workflow run blocks #68 merge) — failed at the same step.Fix: use the actual upstream
v1.14.0SHA, keep the# v1.14.0comment.Why a new PR (not committed onto PR #66's branch)
Standing project rule: no direct commits to
develop. Once this PR merges todevelop, PR #66's diff absorbs both fixes automatically (since #66 isdevelop→main), and the README Copilot thread on #66 can be resolved.Test plan
develop).Publish PyPI library jobsucceeds.