8000 feat: allow using version ranges to cope with stale Maven Local cache by Vampire · Pull Request #1611 · typesafegithub/github-workflows-kt · GitHub
[go: up one dir, main page]

Skip to content

feat: allow using version ranges to cope with stale Maven Local cache #1611

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

Merged
merged 4 commits into from
Feb 25, 2025

Conversation

Vampire
Copy link
Collaborator
@Vampire Vampire commented Aug 19, 2024

With these changes you can for example depend on actions:cache__save___major:[v4,v5)" and get the latest v4 action with latest v4 typing by resolving to a concrete v4.x.y version but the output still contains just v4.
The same for actions:cache__save___minor:[v4.0,v4.1), to get the latest v4.0 but in the output just have v4.0.

Copy link
Collaborator Author
Vampire commented Aug 19, 2024

@Vampire Vampire force-pushed the vampire/version-range-support branch from bfe88c2 to 5f291dc Compare August 19, 2024 15:21
@Vampire Vampire force-pushed the vampire/fix-metadata-file branch from ba37150 to 6ca3d30 Compare August 19, 2024 18:26
@Vampire Vampire force-pushed the vampire/version-range-support branch from 5f291dc to 09633a4 Compare August 19, 2024 18:26
@Vampire Vampire force-pushed the vampire/fix-metadata-file branch from 6ca3d30 to af0de7b Compare August 20, 2024 10:46
@Vampire Vampire force-pushed the vampire/version-range-support branch from 09633a4 to cb4a8a3 Compare August 20, 2024 10:46
@Vampire Vampire force-pushed the vampire/fix-metadata-file branch from af0de7b to 80db505 Compare August 20, 2024 11:26
@Vampire Vampire force-pushed the vampire/version-range-support branch from cb4a8a3 to d9a036e Compare August 20, 2024 11:26
@Vampire Vampire force-pushed the vampire/fix-metadata-file branch from 80db505 to 6df8a27 Compare August 20, 2024 11:57
@Vampire Vampire force-pushed the vampire/version-range-support branch from d9a036e to a7e496f Compare August 20, 2024 11:58
@Vampire Vampire force-pushed the vampire/fix-metadata-file branch from 6df8a27 to cd832fe Compare August 22, 2024 00:00
@Vampire Vampire force-pushed the vampire/version-range-support branch from a7e496f to ef9782d Compare August 22, 2024 00:00
@Vampire Vampire force-pushed the vampire/fix-metadata-file branch from cd832fe to c8aeae6 Compare August 22, 2024 00:27
krzema12 added a commit that referenced this pull request Feb 24, 2025
Related to
#1611.

We're going to make some changes in the function, so let's add some
safety net to prevent regressions + a way to see how the modified
function behaves.

---------

Co-authored-by: Björn Kautler <Bjoern@Kautler.net>
@Vampire Vampire changed the base branch from main to graphite-base/1611 February 24, 2025 10:09
@Vampire Vampire force-pushed the vampire/version-range-support branch from 26c5bb1 to d0a6ac3 Compare February 24, 2025 10:09
@Vampire Vampire changed the base branch from graphite-base/1611 to vampire/fix-version-comparison February 24, 2025 10:09
@Vampire Vampire changed the base branch from vampire/fix-version-comparison to graphite-base/1611 February 24, 2025 10:14
@Vampire Vampire force-pushed the vampire/version-range-support branch from d0a6ac3 to 3f9ac7d Compare February 24, 2025 10:15
@Vampire Vampire changed the base branch from graphite-base/1611 to vampire/fix-version-comparison February 24, 2025 10:15
@Vampire Vampire requested a review from krzema12 February 24, 2025 10:21
Base automatically changed from vampire/fix-version-comparison to main February 24, 2025 11:12
@Vampire Vampire force-pushed the vampire/version-range-support branch from 3f9ac7d to 9321528 Compare February 24, 2025 12:37
Copy link
Member
@krzema12 krzema12 left a comment

Choose a reason for hiding this comment

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

I think this is the last review round 😄

@Vampire Vampire force-pushed the vampire/version-range-support branch from 9321528 to 2cbfbfc Compare February 24, 2025 21:41
Copy link
Collaborator Author
Vampire commented Feb 25, 2025

We'll see :-D

@Vampire Vampire requested a review from krzema12 February 25, 2025 02:44
@Vampire Vampire force-pushed the vampire/version-range-support branch from e161253 to 9a0da25 Compare February 25, 2025 02:49
Copy link
Member
@krzema12 krzema12 left a comment

Choose a reason for hiding this comment

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

Final2.txt

@Vampire Vampire requested a review from krzema12 February 25, 2025 10:16
@krzema12 krzema12 changed the title feat(abg): allow usage of version ranges by generating only major or minor version even with more detailed version feat: allow usage of version ranges to cope with stale Maven Local cache Feb 25, 2025
@krzema12 krzema12 changed the title feat: allow usage of version ranges to cope with stale Maven Local cache feat: allow using version ranges to cope with stale Maven Local cache Feb 25, 2025
@krzema12 krzema12 merged commit c384f47 into main Feb 25, 2025
15 checks passed
@krzema12 krzema12 deleted the vampire/version-range-support branch February 25, 2025 10:22
@krzema12
Copy link
Member

@Vampire thanks, and sorry for the long wait - I'm trying my best to reduce the backlog of PRs 😄 I think the strategy to focus on mutually iterating on a single PR works really well, lets me focus properly.

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.

2 participants
0