Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scan new versions for existing libraries #552

Merged
merged 23 commits into from
Nov 12, 2024

Conversation

dnestoro
Copy link
Member

@dnestoro dnestoro commented Oct 25, 2024

What does this PR do?

This PR introduces a new GitHub workflow that scans for newer versions of libraries that currently exist in the repo.
When there is a newer version available, we are trying to run existing tests with existing metadata to verify if tests can pass.

  • In case when existing tests can pass using the newer version of the library, the workflow will automatically update tested-versions list in the corresponding index.json file. Accumulated results will be provided through an automatically created PR.
  • Otherwise, when tests cannot pass with existing metadata for newer library version, workflow will store this information and create an issue with accumulated information about all unsupported versions.

NOTE: we must allow github actions to create PRs automatically.

@dnestoro dnestoro self-assigned this Oct 25, 2024
@dnestoro dnestoro requested a review from a team as a code owner October 25, 2024 16:33
@dnestoro dnestoro requested review from msupic and removed request for msupic October 25, 2024 16:33
@dnestoro dnestoro force-pushed the dnestoro/CreateLibraryVersionsDependabot branch from 7c25881 to 2a338c9 Compare October 30, 2024 13:28
@dnestoro dnestoro force-pushed the dnestoro/CreateLibraryVersionsDependabot branch from f61dc30 to 0841c01 Compare October 30, 2024 13:56
@vjovanov
Copy link
Member

This PR requires a detailed explanation (in the form of docs) on how the new version is computed.

@dnestoro
Copy link
Member Author

dnestoro commented Nov 7, 2024

This PR requires a detailed explanation (in the form of docs) on how the new version is computed.

Maybe we should start some kind of infrastructure changelog?

Copy link
Member

@melix melix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functionally-wise, sounds good to me. The implementation however needs a couple reworks to be Gradle idiomatic (and not break up-to-date checking/configuration).

Copy link
Member

@melix melix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Almost there, almost there!

@dnestoro dnestoro requested a review from melix November 8, 2024 13:59
@dnestoro dnestoro merged commit 6d740fe into master Nov 12, 2024
228 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.

4 participants