Skip to content

ci: update core-build workflow actions to current majors - #96

Open
katsugtgz wants to merge 2 commits into
lfedgeai:mainfrom
katsugtgz:ci/update-core-build-actions
Open

ci: update core-build workflow actions to current majors#96
katsugtgz wants to merge 2 commits into
lfedgeai:mainfrom
katsugtgz:ci/update-core-build-actions

Conversation

@katsugtgz

@katsugtgz katsugtgz commented Sep 4, 2026

Copy link
Copy Markdown

Updates the CI workflow to use current GitHub-maintained action versions.

Changes:

  • actions/checkout@v4 -> actions/checkout@v7
  • actions/setup-python@v4 -> actions/setup-python@v7 (the pip-install input is not used in this workflow)
  • docker/setup-buildx-action@v2 -> docker/setup-buildx-action@v4
  • commented-out actions/setup-go@v4 reference updated to v7 so nothing in the file stays on an old major (no functional change)

Validation:

  • actionlint 1.7.12 passes on the updated workflow
  • YAML parse check passes

Scope: .github/workflows/core-build.yaml only. release.yaml was left untouched since it is a release workflow. Commit author katsugtgz, unsigned.

actions/checkout v4 to v7, actions/setup-python v4 to v7,
docker/setup-buildx-action v2 to v4.

Scope: .github/workflows/core-build.yaml only.
@katsugtgz
katsugtgz force-pushed the ci/update-core-build-actions branch from 088ca30 to 4f1ef44 Compare September 7, 2026 11:38
@katsugtgz

Copy link
Copy Markdown
Author

Sorry for the churn. One more fix on this branch: bumped a commented-out actions/setup-go reference to v7 so nothing in the file is left on an old major. No functional change.

@wilsonwang371

Copy link
Copy Markdown
Collaborator

what is the purpose of this change?

@katsugtgz

Copy link
Copy Markdown
Author

Sorry for the churn on this branch. To answer the question: the active steps referenced old action majors (checkout v4, setup-python v4, buildx v2). This update moves them to the current majors (v7, v7, v4). One more push today fixed the commented-out setup-go line to v7 as well. No functional change to the build.

@wilsonwang371

Copy link
Copy Markdown
Collaborator

I don't think this is a must fix right now.

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.

2 participants