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

ansible-lint, yamllint: Update revision and interpreter to python3.13 #27172

Merged
merged 5 commits into from
Feb 3, 2025

Conversation

jhoyt4
Copy link
Contributor

@jhoyt4 jhoyt4 commented Dec 21, 2024

Update ansible-lint and yamlint to use python 3.13

Additionally:
ansible-lint: update to 24.12.2 use python 3.13
yamlint: add python 3.13
py-bracecx: update to 2.5 and add python 3.13
py-enrich: add python 3.13
py-wcmatch: update to 10.0 and add python 3.13

Description

Update yamlint and ansible-lint to the latest python (3.13)

Type(s)
  • bugfix
  • enhancement
  • security fix
Tested on

macOS 15.1.1 24B91 arm64
Xcode 16.2 16C5032a

Verification

Have you

  • followed our Commit Message Guidelines?
  • squashed and minimized your commits?
  • checked that there aren't other open pull requests for the same change?
  • referenced existing tickets on Trac with full URL in commit message?
  • checked your Portfile with port lint?
  • tried existing tests with sudo port test?
  • tried a full install with sudo port -vst install?
  • tested basic functionality of all binary files?
  • checked that the Portfile's most important variants haven't been broken?

@macportsbot
Copy link

Notifying maintainers:
@zdw for port ansible-lint.
@judaew for port yamllint, py-bracex, py-enrich, py-wcmatch, ansible-lint.
@danchr for port py-black.

@jhoyt4 jhoyt4 marked this pull request as draft December 21, 2024 14:27
@jhoyt4
Copy link
Contributor Author

jhoyt4 commented Dec 21, 2024

This PR requires PR27172 or similar to be accepted before it can go any further

@reneeotten
Copy link
Contributor

the change to Python 3.13 should happen only after MacPorts has changed its default Python version. That happens on January 1st each year.

@jhoyt4
Copy link
Contributor Author

jhoyt4 commented Dec 23, 2024

@reneeotten - thanks for the heads up. I can keep this here for another week. It's also still blocked by PR27171 which gets a version of ansible that works with python313

I'll leave this as a draft until all the criteria are properly met.

@jhoyt4 jhoyt4 changed the title ansible-lint, yamllint: Update revision and interpreter to python3.13 WIP: ansible-lint, yamllint: Update revision and interpreter to python3.13 Dec 28, 2024
@jhoyt4 jhoyt4 force-pushed the yamllint branch 3 times, most recently from ec74eb4 to 811f1fe Compare January 31, 2025 00:50
@jhoyt4 jhoyt4 changed the title WIP: ansible-lint, yamllint: Update revision and interpreter to python3.13 ansible-lint, yamllint: Update revision and interpreter to python3.13 Jan 31, 2025
@jhoyt4 jhoyt4 marked this pull request as ready for review January 31, 2025 01:17
devel/yamllint/Portfile Outdated Show resolved Hide resolved
sysutils/ansible-lint/Portfile Show resolved Hide resolved
sysutils/ansible-lint/Portfile Outdated Show resolved Hide resolved
@jhoyt4
Copy link
Contributor Author

jhoyt4 commented Feb 2, 2025

@reneeotten - that last force push should clean up 2 of your three requested changes.

It appears ansible-lint does in fact require importlib-metadata

@reneeotten
Copy link
Contributor

@reneeotten - that last force push should clean up 2 of your three requested changes.

It appears ansible-lint does in fact require importlib-metadata

looks, good. However by now these do not appear to be the latest versions anymore (at least not for ansible-lint), so please update to the latest upstream versions where applicable and we'll merge the PR.

@jhoyt4
Copy link
Contributor Author

jhoyt4 commented Feb 2, 2025

updated. ansible-lint and bracex now at the latest versions.

@reneeotten reneeotten merged commit 507cee6 into macports:master Feb 3, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

5 participants