Skip to content

Fix FromSource_SkipRebuild_Verify dependency resolution failures#48475

Draft
raych1 wants to merge 1 commit intomainfrom
fix/from-source-skip-rebuild-dependency-resolution
Draft

Fix FromSource_SkipRebuild_Verify dependency resolution failures#48475
raych1 wants to merge 1 commit intomainfrom
fix/from-source-skip-rebuild-dependency-resolution

Conversation

@raych1
Copy link
Member

@raych1 raych1 commented Mar 19, 2026

Problem

The FromSource_SkipRebuild_Verify CI job consistently fails. The Build for From Source run step can't resolve dependencies at their current (unreleased) versions.

Fix

  1. initialize-test-environment.yml: Moved generate_from_source_pom.py to run before set_versions/update_versions, added --match-any-version flag
  2. code-quality-reports.yml and archetype-sdk-client-patch.yml: Added --match-any-version flag

The --match-any-version flag matches POM dependency versions against both the released (dependency) and development (current) versions in version_client.txt.

Run generate_from_source_pom.py before set_versions/update_versions in
initialize-test-environment.yml and add --match-any-version flag to all
callers so the script matches POM dependency versions against both the
released (dependency) and development (current) versions in
version_client.txt.

This ensures inter-repo dependencies are correctly identified even when
POM dependency tags reference the released version while the library's
current version has been bumped.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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