GeezerVison is showing github.com — chore: Adjusting the file version validation for minor releases by franciscojavierarceo · Pull Request #4221 · feast-dev/feast
Conversation
What this PR does / why we need it:
This is changing the validation to ignore patch version changes. So the CI should trigger correctly for increments from 0.37.1 -> 0.38.0.
python infra/scripts/release/bump_file_versions.py 0.37.0 0.38.0
Updated 16 files with new version 0.38.0
Previously this failed as 0.37.1 wasn't recognized as a tag.
Which issue(s) this PR fixes:
Fixes
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
franciscojavierarceo
changed the title
chore: adjusting the file version validation for minor releases
chore: Adjusting the file version validation for minor releases
May 23, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Despite validation, this is still not going to work, as line 48 looks for the passed current_version to replace in files. I think much easier solution is to simply revert version bumps.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Despite validation, this is still not going to work, as line 48 looks for the passed current_version to replace in files. I think much easier solution is to simply revert version bumps.
The version bumps are automatically generated through this code. Are you suggesting we do that for every patch release @tokoko?
Also, I'll fix line 48.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
@franciscojavierarceo No, version bumps to 0.37.1 was automatic, but not on master, it was done on v-0.37-branch. We manually introduced those version bumps to master with a later PR (#4127) which was a mistake. I don't mind if we scrap validation from the scripts either, just pointing out that it's unnecessary if we simply revert some of the changes from that PR (version bumps specifically).
|
franciscojavierarceo reacted with thumbs up emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
We manually introduced those version bumps to master with a later PR (#4127) which was a mistake.
Got it! I missed this, my bad. Lack of sleep 🥲 .
|
tokoko reacted with thumbs up emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|