Skip to content

project release: fall back to another instance's release version when the owner has none - #147

Merged
rjd15372 merged 1 commit into
mainfrom
merge-release-fallback
Oct 14, 2026
Merged

rjd15372 merged 1 commit into
mainfrom
merge-release-fallback

Conversation

@rjd15372

Copy link
Copy Markdown
Collaborator

Follow-up to #146. Labs holds the current staging of the UBI slice
(h3, the container images) but has no ppg:releases:17 project at all:
the previous release was cut entirely from build.opensuse.org. The
paired merge rule discarded boo's release values for keys owned by
labs, so every such package was reported as "added" and every image
as a full dump instead of an update diff.

A key's release value now comes from the owning instance when it has
one (a stale copy elsewhere still never shadows it), otherwise from the
first instance that has it. Verified shape in a test: boo release
4.4.0-1 + labs source 4.5.0-1 → "h3 (extras): update upstream version
4.5.0". 656 tests, black, pyright 0 errors.

…ned keys

Signed-off-by: Ricardo Dias <ricardo.dias@percona.com>
@rjd15372
rjd15372 merged commit 080f216 into main Oct 14, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant