chore: auto-refresh reusable workflow tags#1192
Merged
Conversation
stranske
temporarily deployed
to
agent-high-privilege
GitHub Actions
Inactive
Contributor
Automated Status SummaryHead SHA: 4f76694
Coverage Overview
Coverage Trend
Top Coverage Hotspots (lowest coverage)
Updated automatically; will refresh on subsequent CI/Docker completions. Keepalive checklistScopeAfter merging PR #103 (multi-agent routing infrastructure), we need to:
Context for AgentDesign Decisions & Constraints
Related Issues/PRsReferencesBlockers & Dependencies
TasksPipeline Validation
GITHUB_STEP_SUMMARY
Conditional Status Summary
Comment Pattern Cleanup
Acceptance criteria
|
stranske
temporarily deployed
to
agent-high-privilege
GitHub Actions
Inactive
- Replace sed with parameter expansion to fix SC2001 - Add maint-70-refresh-reusable-tags.yml to test expectations - Document workflow in WORKFLOWS.md and WORKFLOW_SYSTEM.md
Contributor
🤖 Keepalive Loop StatusPR #1192 | Agent: Codex | Iteration 0/5 Current State
🔍 Failure Classification| Error type | infrastructure | |
github-actions
bot
added
the
autofix
Contributor
|
Status | ✅ no new diagnostics |
stranske
temporarily deployed
to
agent-high-privilege
GitHub Actions
Inactive
Contributor
There was a problem hiding this comment.
Pull request overview
This PR introduces a new maintenance workflow to automatically update the v1 floating tag to track the main branch HEAD after every merge, enabling consumer repositories to automatically receive the latest reusable workflow changes without manual version bumps. This addresses the issue where bug fixes (like the rate-limit remediation in PR #1183) don't propagate to consumer repos that pin workflows to @v1.
Changes:
- Adds
maint-70-refresh-reusable-tags.ymlworkflow that force-pushes the v1 tag to main branch HEAD on every push to main - Documents the new auto-refresh behavior in
docs/ops/CONSUMER_REPO_MAINTENANCE.md - Changes the v1 versioning strategy from tracking releases (v1.x) to tracking main branch HEAD
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| .github/workflows/maint-70-refresh-reusable-tags.yml | New workflow that automatically updates floating tags (default: v1) to main HEAD after every merge |
| docs/ops/CONSUMER_REPO_MAINTENANCE.md | Documents the new reusable workflow versioning behavior and manual trigger instructions |
Contributor
✅ Codex Completion CheckpointCommit: No new completions recorded this round. About this commentThis comment is automatically generated to track task completions. |
agents-workflows-bot
bot
temporarily deployed
to
agent-high-privilege
- Rename workflow from maint-70 to maint-73 to avoid number conflict - Fix summary to only report when tags actually updated - Update INTEGRATION_GUIDE.md to document main-tracking strategy - Update COMPATIBILITY.md to reflect v1 tracks main HEAD - Deprecate maint-61 (conflicts with main-tracking strategy) - Clarify version strategy change in CONSUMER_REPO_MAINTENANCE.md - Update all documentation references to maint-73
stranske
temporarily deployed
to
agent-high-privilege
GitHub Actions
Inactive
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
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.
Automated Status Summary
Scope
After merging PR #103 (multi-agent routing infrastructure), we need to:
GITHUB_STEP_SUMMARYoutput so iteration results are visible in the Actions UIContext for Agent
Design Decisions & Constraints
<!-- keepalive-loop-summary -->| github-actions[bot] | NEW: CLI agent iteration tracking | ✅ Keep for CLI agents |<!-- keepalive-state:v1 -->| agents-workflows-bot[bot] | State tracking |<!-- keepalive-round: N -->| stranske | OLD: Instruction comment | ❌ CLI agents dont need this |agent:*label), we should have exactly one updating comment (<!-- keepalive-loop-summary -->) instead of accumulating 10+ comments per PR.Related Issues/PRs
References
Blockers & Dependencies
Tasks
Pipeline Validation
agent:codexlabelGITHUB_STEP_SUMMARY
agents-keepalive-loop.ymlafter agent runConditional Status Summary
buildStatusBlock()inagents_pr_meta_update_body.jsto acceptagentTypeparameteragentTypeis set (CLI agent): hide workflow table, hide head SHA/required checksComment Pattern Cleanup
agent:*label):<!-- gate-summary: -->comment posting (use step summary instead)<!-- keepalive-round: N -->instruction comments (task appendix replaces this)<!-- keepalive-loop-summary -->to be the single source of truthagent:*label):<!-- gate-summary: -->commentagent_typeoutput to detect job so downstream workflows know the modeagents-pr-meta.ymlto conditionally skip gate summary for CLI agent PRsAcceptance criteria
Head SHA: 95ceb7b
Latest Runs: ✅ success — Gate
Required: gate: ✅ success