Skip to content

fix: resolve merge conflict markers in CI workflows and upgrade Actions#742

Open
haoyu-haoyu wants to merge 1 commit intoBindsNET:masterfrom
haoyu-haoyu:fix/ci-merge-conflicts
Open

fix: resolve merge conflict markers in CI workflows and upgrade Actions#742
haoyu-haoyu wants to merge 1 commit intoBindsNET:masterfrom
haoyu-haoyu:fix/ci-merge-conflicts

Conversation

@haoyu-haoyu
Copy link
Copy Markdown

Summary

The CI workflows currently contain unresolved git merge conflict markers (<<<<<<< HEAD, =======, >>>>>>> origin), making all CI checks non-functional.

  • Resolve conflicts in python-app.yml and pythonpackage.yml by choosing the origin side: Python 3.13 in the test matrix, Poetry 2.1.2. This is consistent with pyproject.toml (python = ">=3.10,<3.14") and merged PR Support Python 3.13 #710 (Python 3.13 support).

  • Upgrade GitHub Actions across all 3 workflow files:

    • actions/checkout: v2/v3 → v4
    • actions/setup-python: v2/v4 → v5

Test plan

  • CI workflows should now parse as valid YAML
  • Test matrix should cover Python 3.10, 3.11, 3.12, 3.13

- Resolve unmerged git conflict markers in python-app.yml and
  pythonpackage.yml by choosing the origin side (Python 3.13
  support, Poetry 2.1.2), consistent with pyproject.toml and
  merged PR BindsNET#710.

- Upgrade actions/checkout from v2/v3 to v4 and
  actions/setup-python from v2/v4 to v5 across all 3 workflows.
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.

1 participant