Add release drift check to PR tracking report - #11
Merged
Conversation
Flags versioned-plugins (per GitHub topic) with commits on their default branch beyond the latest GitHub Release, so we don't lose track of a plugin needing a cut before the next Rundeck/Rundeckpro GA. Runs daily alongside the existing PR report and appends to the same file/branch.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR extends the existing daily PR tracking workflow by appending a “Release Drift” section to the same pr-tracking/$today.md report, intended to identify versioned-plugins repositories whose default branch has commits beyond the latest GitHub Release.
Changes:
- Adds a “Check Release Drift” step (with
continue-on-error: true) that enumeratesversioned-pluginsrepos and computesahead_byvs the latest GitHub Release tag. - Appends a markdown table + summary counts to the daily report file.
- Introduces a separate daily
pr-tracking/release-drift-history.csvfor tracking drift counts over time.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+217
to
+220
| latest=$(gh release view --repo rundeck-plugins/$repo --json tagName -q .tagName 2>/dev/null || true) | ||
| if [ -z "$latest" ]; then | ||
| continue # never released (examples/demos/tooling repos) - not a drift candidate | ||
| fi |
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.
What
Adds a "Check Release Drift" step to the daily PR tracking workflow. It flags
plugins tagged with the
versioned-pluginsGitHub topic that have commits ontheir default branch beyond the latest GitHub Release.
Why
We want to know which plugins need a release cut before the next Rundeck /
Rundeckpro GA, without adding a second report to check. This appends a
"Release Drift" section into the same daily
pr-tracking/$today.mdfile andbranch the team already reads, rather than a separate workflow/branch.
Notes
versioned-pluginsrepo topic (25 repos: the full plugininventory in PLUGINS_OVERVIEW.md), not "has any GitHub release" - that
excluded tooling/example repos (build-zip, ui-job-metrics, etc.) that
happen to carry semver tags for unrelated reasons.
"latest released version," matching the convention already established
in skills/rundeck-plugin-versions.
Verified cost: ~60-120 gh/API calls, under a minute, well under the
Actions token's per-repo rate limit.
continue-on-error: trueon the step so a bug here can't take down thedaily PR report.