You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: renovate readiness check unicorn pepr image version (#2062)
## Description
The current implementation only checks the REGISTRY1_PEPR_IMAGE version
against package.json, only validates that registry1 matches
package.json, but doesn't check if unicorn is also in sync.
I've updated the Pepr version checking logic in the renovate readiness
action to validate that all three Pepr versions are in sync.
## Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Other (security config, docs update, etc)
## Checklist before merging
- [x] Test, docs, adr added or updated as needed
- [x] [Contributor
Guide](https://github.com/defenseunicorns/uds-template-capability/blob/main/CONTRIBUTING.md)
followed
Copy file name to clipboardExpand all lines: .github/actions/renovate-readiness/README.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,16 @@ The action performs the following steps:
15
15
2.**Branch Name Processing**: The action extracts the package name from the branch name by removing the `renovate/` prefix.
16
16
17
17
3.**Special Case Handling**:
18
-
-**Pepr Updates**: For Pepr updates, the action compares the version in `package.json` with the image versions in `tasks/create.yaml`. If they don't match, it adds the `waiting on ironbank` label.
18
+
-**Pepr Updates**: For Pepr updates, the action validates that all three Pepr versions are in sync:
19
+
-`package.json` dependency version
20
+
-`REGISTRY1_PEPR_IMAGE` in `tasks/create.yaml`
21
+
-`UNICORN_PEPR_IMAGE` in `tasks/create.yaml`
22
+
23
+
The action applies specific labels based on which versions are out of sync:
24
+
-`waiting on upstream`: If package.json version is behind both/either image versions (indicates a Pepr release issue)
25
+
-`waiting on ironbank`: If Ironbank image is behind package.json
26
+
-`waiting on unicorn`: If Unicorn image is behind package.json
27
+
- Multiple `waiting on` labels can be applied if multiple images are behind
19
28
-**Support Dependencies**: For support dependency updates, the action adds the `needs-review` label and sets `should_process` to `false` to prevent excessive IAC runs.
MANAGED_LABELS=("waiting on ironbank" "waiting on rapidfort" "needs-review" "helm-chart-only" "major-helm-update" "major-image-update")
254
+
MANAGED_LABELS=("waiting on upstream" "waiting on ironbank" "waiting on unicorn" "waiting on rapidfort" "needs-review" "helm-chart-only" "major-helm-update" "major-image-update")
203
255
204
256
# Remove labels that are currently on the PR but not in the new set
0 commit comments