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

Update GHA #519

Merged
merged 4 commits into from
Oct 14, 2023
Merged

Update GHA #519

merged 4 commits into from
Oct 14, 2023

Conversation

gforcada
Copy link
Sponsor Member

@gforcada gforcada commented Oct 14, 2023

  • remove Plone 5.2
  • remove Python 3.7
  • add Python 3.10 and 3.11
  • update the actions versions to avoid a deprecation warning

@mister-roboto
Copy link

@gforcada thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

There is a warning that the are about to be deprecated.
- remove Plone 5.2
- remove Python 3.7
- add Python 3.10 and 3.11
@gforcada
Copy link
Sponsor Member Author

As I'm only changing GHA and tox, we don't really need to run the Jenkins jobs.

I'm merging it myself to unlock the other PRs that are currently failing 🍀

@gforcada gforcada merged commit e6c274f into master Oct 14, 2023
9 of 12 checks passed
@gforcada gforcada deleted the gforcada-patch-1 branch October 14, 2023 11:04
@gforcada gforcada mentioned this pull request Oct 14, 2023
@mauritsvanrees
Copy link
Sponsor Member

Thanks.

But declaring 5.2 unsupported, even though no actual code was changed in this PR, is a breaking change: I think up until now the master branch could be used on 5.2 if you use Python 3. This is fine to change, and there is no problem to include this in Plone 6.0.

But can you add a breaking news snippet and bump the version?

@gforcada
Copy link
Sponsor Member Author

Sorry, I missed this for so many months 😖 is it still worth adding now the breaking change news entry, or the ship already sailed? 😓

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.

None yet

3 participants