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

[Qt] update 6.2 to latest version #2266

Merged
merged 1 commit into from
Jan 8, 2023
Merged

[Qt] update 6.2 to latest version #2266

merged 1 commit into from
Jan 8, 2023

Conversation

usta
Copy link
Member

@usta usta commented Jan 8, 2023

@usta usta added the release-updates Pull Requests that update release information label Jan 8, 2023
@usta usta self-assigned this Jan 8, 2023
Copy link
Member

@marcwrobel marcwrobel left a comment

Choose a reason for hiding this comment

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

LGTM, merging.

Looks like the automation configuration will have to be fixed.

@marcwrobel marcwrobel merged commit 597e7fb into master Jan 8, 2023
@marcwrobel marcwrobel deleted the usta-qt branch January 8, 2023 11:52
@marcwrobel
Copy link
Member

marcwrobel commented Jan 8, 2023

Looks like the automation configuration will have to be fixed.

Looked at it, this is not an issue with automation. The 6.2.7 release is only available for commercial users. This page could benefit from an extended support column (#2246).

@usta
Copy link
Member Author

usta commented Jan 8, 2023

@marcwrobel just to know , will our automation redo this version change ? [because it wont be seen in the list] . if yes
we need to add a dont make change if the version is greater than check to our automation

@marcwrobel
Copy link
Member

I think @captn3m0 told me once that version are never downgraded by latest.py. So I would say no, this version change will not be undone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-updates Pull Requests that update release information
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants