Follow-up to #888. The refresh workflow triggered by the merge built ci-claude:2.1.278 (the first version with python3 and py3-yaml, confirmed in the build log) instead of rebuilding 2.1.250, and its bump-pr step failed on a newline in the push token secret (#889), so the consumer bump PR never came.
The wiki-maintenance pipeline needs python for ~/Notes/bin/wiki_ask.py, so it moves to 2.1.278 now; the other consumers follow through the regular bump once #889 is fixed. Lint passes.
After merge I trigger the first run as a deployment and watch every step.
Follow-up to #888. The refresh workflow triggered by the merge built ci-claude:2.1.278 (the first version with python3 and py3-yaml, confirmed in the build log) instead of rebuilding 2.1.250, and its bump-pr step failed on a newline in the push token secret (#889), so the consumer bump PR never came.
The wiki-maintenance pipeline needs python for ~/Notes/bin/wiki_ask.py, so it moves to 2.1.278 now; the other consumers follow through the regular bump once #889 is fixed. Lint passes.
After merge I trigger the first run as a deployment and watch every step.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The refresh triggered by #888 built 2.1.278 (the first ci-claude with
python3) rather than rebuilding 2.1.250, and its bump-pr step failed on
a newline in the push token secret (#889), so the consumer bump never
came. This pipeline needs python for wiki_ask.py, so it moves ahead of
the general bump.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
🤖Automated review — model claude-haiku-4-5-20251001 (complexity: trivial), commit e422e6a13d16b1c415e2453224d775631532d8c0.
Advisory review by the review-bot pipeline. It never approves; a human merges. Push new commits to get a fresh review.
Summary
This PR updates the wiki-maintenance CI pipeline to use ci-claude:2.1.278 instead of 2.1.250 across all four pipeline steps. The change is necessary because 2.1.278 is the first version with Python 3 and py3-yaml support, which is required by the wiki maintenance scripts (~/Notes/bin/wiki_ask.py). The change is straightforward, consistent, and well-justified.
✅ Analysis
Consistency: All four steps in the pipeline are updated uniformly:
checkout-notes: 2.1.250 → 2.1.278
distill: 2.1.250 → 2.1.278
audit: 2.1.250 → 2.1.278
push-notes: 2.1.250 → 2.1.278
No instances of the old version were missed within this file.
Rationale: The PR body clearly explains that this is a follow-up to #888, addressing a specific need for Python 3 support that wasn't available in 2.1.250. Other pipelines remain on 2.1.250 as expected per the PR description — they will be bumped separately once #889 (a token secret formatting issue) is resolved.
Testing: The PR author mentions that linting passes and plans to manually trigger and monitor the first run as a deployment after merge, which is appropriate for CI infrastructure changes.
🟢 Nits
The PR could optionally reference issue #888 in the commit message for better traceability, though the PR body already documents the context clearly.
Recommendation
Looks reasonable — no blocking issues; this is a straightforward version bump with clear justification and a solid verification plan.
🤖 **Automated review** — model `claude-haiku-4-5-20251001` (complexity: trivial), commit `e422e6a13d16b1c415e2453224d775631532d8c0`.
> Advisory review by the `review-bot` pipeline. It never approves; a human merges. Push new commits to get a fresh review.
---
## Summary
This PR updates the wiki-maintenance CI pipeline to use `ci-claude:2.1.278` instead of `2.1.250` across all four pipeline steps. The change is necessary because 2.1.278 is the first version with Python 3 and py3-yaml support, which is required by the wiki maintenance scripts (`~/Notes/bin/wiki_ask.py`). The change is straightforward, consistent, and well-justified.
## ✅ Analysis
**Consistency**: All four steps in the pipeline are updated uniformly:
- `checkout-notes`: 2.1.250 → 2.1.278
- `distill`: 2.1.250 → 2.1.278
- `audit`: 2.1.250 → 2.1.278
- `push-notes`: 2.1.250 → 2.1.278
No instances of the old version were missed within this file.
**Rationale**: The PR body clearly explains that this is a follow-up to #888, addressing a specific need for Python 3 support that wasn't available in 2.1.250. Other pipelines remain on 2.1.250 as expected per the PR description — they will be bumped separately once #889 (a token secret formatting issue) is resolved.
**Testing**: The PR author mentions that linting passes and plans to manually trigger and monitor the first run as a deployment after merge, which is appropriate for CI infrastructure changes.
## 🟢 Nits
The PR could optionally reference issue #888 in the commit message for better traceability, though the PR body already documents the context clearly.
## Recommendation
Looks reasonable — no blocking issues; this is a straightforward version bump with clear justification and a solid verification plan.
<!-- pr-review:sha=e422e6a13d16b1c415e2453224d775631532d8c0 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #888. The refresh workflow triggered by the merge built ci-claude:2.1.278 (the first version with python3 and py3-yaml, confirmed in the build log) instead of rebuilding 2.1.250, and its bump-pr step failed on a newline in the push token secret (#889), so the consumer bump PR never came.
The wiki-maintenance pipeline needs python for ~/Notes/bin/wiki_ask.py, so it moves to 2.1.278 now; the other consumers follow through the regular bump once #889 is fixed. Lint passes.
After merge I trigger the first run as a deployment and watch every step.
🤖 Generated with Claude Code
🤖 Automated review — model
claude-haiku-4-5-20251001(complexity: trivial), commite422e6a13d16b1c415e2453224d775631532d8c0.Summary
This PR updates the wiki-maintenance CI pipeline to use
ci-claude:2.1.278instead of2.1.250across all four pipeline steps. The change is necessary because 2.1.278 is the first version with Python 3 and py3-yaml support, which is required by the wiki maintenance scripts (~/Notes/bin/wiki_ask.py). The change is straightforward, consistent, and well-justified.✅ Analysis
Consistency: All four steps in the pipeline are updated uniformly:
checkout-notes: 2.1.250 → 2.1.278distill: 2.1.250 → 2.1.278audit: 2.1.250 → 2.1.278push-notes: 2.1.250 → 2.1.278No instances of the old version were missed within this file.
Rationale: The PR body clearly explains that this is a follow-up to #888, addressing a specific need for Python 3 support that wasn't available in 2.1.250. Other pipelines remain on 2.1.250 as expected per the PR description — they will be bumped separately once #889 (a token secret formatting issue) is resolved.
Testing: The PR author mentions that linting passes and plans to manually trigger and monitor the first run as a deployment after merge, which is appropriate for CI infrastructure changes.
🟢 Nits
The PR could optionally reference issue #888 in the commit message for better traceability, though the PR body already documents the context clearly.
Recommendation
Looks reasonable — no blocking issues; this is a straightforward version bump with clear justification and a solid verification plan.