Description
The extension registry approval check can incorrectly require core-team review when multiple registry update PRs are open concurrently.
If one PR merges first, another PR's branch still contains the older registry snapshot. The check compares the latest base registry with that stale snapshot and reports the newly merged release as removed:
extension '<extension>' release '<version>' was removed; published releases are immutable
The PR did not remove or modify that release, so rebasing or merging main is currently required only to make the check pass.
Expected behaviour
The check should evaluate the registry as it would exist after the PR is merged. Unrelated releases merged by concurrent PRs should remain present, while genuine release removals or modifications introduced by the PR must still require core-team review.
Description
The extension registry approval check can incorrectly require core-team review when multiple registry update PRs are open concurrently.
If one PR merges first, another PR's branch still contains the older registry snapshot. The check compares the latest base registry with that stale snapshot and reports the newly merged release as removed:
The PR did not remove or modify that release, so rebasing or merging
mainis currently required only to make the check pass.Expected behaviour
The check should evaluate the registry as it would exist after the PR is merged. Unrelated releases merged by concurrent PRs should remain present, while genuine release removals or modifications introduced by the PR must still require core-team review.