-
Notifications
You must be signed in to change notification settings - Fork 765
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
Latest Versions Oct2024 #1925
Latest Versions Oct2024 #1925
Conversation
emanlove
commented
Nov 1, 2024
- Fixes the cookie tests which need to be updated each year because Chrome, at least, does not allow cookies to expire further out than a year.
- Updates upload-artifacts to supported version 3. Have not moved to version 4 due to need to update artifact naming convention. (Will need to do this soon as V3 is also being deprecated)
- Updated Python version to include 3.13.0, robot framework v7.1.1, and selenium 4.24.0, 4.25.0, and 4.26.1
As Chrome does not allow for cookie expiry to not go out past a year we need to update each September. This is the update for September 2024. Also left instruction on how to update so next year it is even easier.
…d Selenium Update to .. - Python up to now 3.13.0rc2 - Robot Framework from 7.0.1 to 7.1 - Selenium 4.23.1, 4.24.0, 4.25.0
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.
Can we not calculate the cookie dates so this doesn't have to be updated every year?
It should be possible with Robots DateTime library |
Yeah .. we should. As I recall the one which expires in September, there is something about UTC time within the script/check that made it fail depending on where it was run. So on my local it would be one time and then in GitHub Action it was another. So knowing what time it was independent of the test became a pain. Will relook at this .. |