Merged
Conversation
📝 WalkthroughWalkthroughVersion bump from v0.2.0-zig-edge.29 to v0.2.0-zig-edge.31 applied across documentation, package manifests, and workflow files. Introduces ReleaseTag parameter to docs-status-check script with enhanced tag resolution logic supporting direct input, package.json inference, and GitHub API fallback for version-aware validation. Changes
Sequence Diagram(s)sequenceDiagram
participant Workflow as Release Workflow
participant Script as docs-status-check.ps1
participant PkgJson as package.json
participant GitHubAPI as GitHub API
participant Docs as Documentation Files
Workflow->>Script: Invoke with ReleaseTag parameter
alt ReleaseTag provided
Script->>Script: Use ReleaseTag directly
else ReleaseTag empty
Script->>PkgJson: Read version from package.json
PkgJson-->>Script: Return version (if found)
alt Version found
Script->>Script: Set releaseTag from package.json
else Version not found
Script->>GitHubAPI: Query latest edge release
GitHubAPI-->>Script: Return release metadata
Script->>Script: Set releaseTag from API result
end
end
Script->>Docs: Validate docs reference "Current edge release target tag"
Docs-->>Script: Validation result
Script-->>Workflow: Return validation status
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/zig-port/PORT_PLAN.md (1)
223-238:⚠️ Potential issue | 🟡 MinorFix stale edge tag mention in the same release-status block.
Line 238 still references
edge.29while this section now targetsv0.2.0-zig-edge.31(Line 223, Line 237). Please update that sentence to avoid conflicting operator guidance.🛠️ Suggested doc fix
- - npm public publish remains externally blocked by npm scope/package permission on npmjs; the edge.29 tarball is attached to the GitHub prerelease and the GitHub Packages fallback path ran successfully. + - npm public publish remains externally blocked by npm scope/package permission on npmjs; the edge.31 tarball is attached to the GitHub prerelease and the GitHub Packages fallback path ran successfully.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/zig-port/PORT_PLAN.md` around lines 223 - 238, Update the stale tag reference in the release-status block so it matches the current target tag `v0.2.0-zig-edge.31`: find the sentence that mentions `edge.29` (within the release evidence / release-status section) and replace `edge.29` with `v0.2.0-zig-edge.31` (or reword to reference the current edge tag variable) so the statement about the attached tarball and GitHub prerelease aligns with the earlier lines that reference `v0.2.0-zig-edge.31`.
🧹 Nitpick comments (1)
docs/zig-port/PHASE_CHECKLIST.md (1)
5-5: Consider anchoring this validation claim with a date/run reference.The branch-local validation statement is useful, but adding a timestamp or workflow run ID would reduce staleness and improve traceability over time.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/zig-port/PHASE_CHECKLIST.md` at line 5, Update the validation sentence that mentions "Current edge release target: `v0.2.0-zig-edge.31`" to include a concrete provenance marker (e.g., ISO 8601 date/time and/or CI workflow run ID) so the claim is traceable; modify the line to append "(validated locally on <YYYY-MM-DDTHH:MM:SSZ> / CI run: <workflow-name>#<run-id>)" or similar and ensure the added timestamp/run ID format is consistent with other docs.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@docs/zig-port/PORT_PLAN.md`:
- Around line 223-238: Update the stale tag reference in the release-status
block so it matches the current target tag `v0.2.0-zig-edge.31`: find the
sentence that mentions `edge.29` (within the release evidence / release-status
section) and replace `edge.29` with `v0.2.0-zig-edge.31` (or reword to reference
the current edge tag variable) so the statement about the attached tarball and
GitHub prerelease aligns with the earlier lines that reference
`v0.2.0-zig-edge.31`.
---
Nitpick comments:
In `@docs/zig-port/PHASE_CHECKLIST.md`:
- Line 5: Update the validation sentence that mentions "Current edge release
target: `v0.2.0-zig-edge.31`" to include a concrete provenance marker (e.g., ISO
8601 date/time and/or CI workflow run ID) so the claim is traceable; modify the
line to append "(validated locally on <YYYY-MM-DDTHH:MM:SSZ> / CI run:
<workflow-name>#<run-id>)" or similar and ensure the added timestamp/run ID
format is consistent with other docs.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: c6d9da17-e207-43ed-ad85-56985d3585d6
📒 Files selected for processing (15)
.github/workflows/release-preview.ymlREADME.mddocs/index.mddocs/operations.mddocs/package-publishing.mddocs/zig-port/FULL_STACK_REPLACEMENT_MATRIX.mddocs/zig-port/PHASE_CHECKLIST.mddocs/zig-port/PORT_PLAN.mdnpm/openclaw-zig-rpc-client/README.mdnpm/openclaw-zig-rpc-client/package.jsonpython/openclaw-zig-rpc-client/README.mdpython/openclaw-zig-rpc-client/pyproject.tomlscripts/docs-status-check.ps1scripts/release-preview.ps1scripts/release-status.ps1
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 by CodeRabbit