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

add windows-2025 to the build matrix #2039

Merged
merged 1 commit into from
Dec 20, 2024
Merged

Conversation

shogo82148
Copy link
Owner

@shogo82148 shogo82148 commented Dec 20, 2024

https://github.blog/changelog/2024-12-19-windows-server-2025-is-now-in-public-preview/

Summary by CodeRabbit

  • New Features
    • Expanded testing environment with additional operating system support for Windows and Strawberry distributions.
  • Bug Fixes
    • Commented out a problematic test step in the Darwin job to address a known issue on macOS.
  • Chores
    • Overall workflow structure remains intact with no changes to existing job logic or commands.

Copy link

coderabbitai bot commented Dec 20, 2024

Walkthrough

The pull request updates the GitHub Actions workflow configuration in .github/workflows/test.yml to expand testing environments. The changes include adding support for windows-2025 in the test-windows and test-strawberry jobs, broadening the range of operating systems used for testing. Additionally, a test step running Perl in a Python shell has been commented out in the test-darwin job due to a known issue on macos-13. The core workflow structure and test execution process remain unchanged.

Changes

File Change Summary
.github/workflows/test.yml - Added windows-2025 to test-windows job matrix
- Added windows-2022 and windows-2025 to test-strawberry job matrix
- Commented out Perl test step in test-darwin job due to macos-13 issue

Possibly related PRs

Poem

🐰 Workflows dance, new systems arise,
Windows 2025 joins our testing prize!
Macos whispers, a step now at rest,
Our CI pipeline continues its quest!
Hopping through versions with rabbitly glee 🚀


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 05ec910 and 39e9400.

📒 Files selected for processing (1)
  • .github/workflows/test.yml (2 hunks)
🧰 Additional context used
🪛 actionlint (1.7.4)
.github/workflows/test.yml

187-187: label "windows-2025" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)


272-272: label "windows-2025" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

Comment on lines +271 to +272
- windows-2022
- windows-2025
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Mixed change: Valid windows-2022 but invalid windows-2025

  • ✅ Adding windows-2022 is good as it's a supported runner
  • windows-2025 is not a supported GitHub-hosted runner

Please update the matrix to keep only the supported runners:

  matrix:
    os:
      - windows-2019
      - windows-2022
-     - windows-2025
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- windows-2022
- windows-2025
- windows-2019
- windows-2022
🧰 Tools
🪛 actionlint (1.7.4)

272-272: label "windows-2025" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

@@ -184,6 +184,7 @@
os:
- windows-2019
- windows-2022
- windows-2025
Copy link

@coderabbitai coderabbitai bot Dec 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Invalid runner label: windows-2025 is not a supported GitHub-hosted runner

The runner label windows-2025 is not recognized by GitHub Actions. The latest supported Windows runner is windows-2022. Using an unsupported runner will cause the workflow to fail.

Please update the matrix to use only supported runners:

  matrix:
    os:
      - windows-2019
      - windows-2022
-     - windows-2025

For reference, see GitHub's documentation on supported runners.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- windows-2025
- windows-2019
- windows-2022
🧰 Tools
🪛 actionlint (1.7.4)

187-187: label "windows-2025" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)


💡 Codebase verification

Invalid runner labels detected in workflow configuration

Multiple instances of invalid runner labels found:

  • windows-2025 (no such runner exists)
  • macos-15 (no such runner exists)

The following runners are valid and commonly used:

  • ubuntu-24.04, ubuntu-22.04, ubuntu-20.04
  • macos-14, macos-13
  • windows-2019, windows-2022

Consider replacing:

  • windows-2025 with windows-latest or windows-2022
  • macos-15 with macos-latest or macos-14
🔗 Analysis chain

Verify runner compatibility across the workflow

Let's verify the compatibility of all runners used in this workflow.

To maintain workflow stability:

  1. Always verify runner labels against GitHub's official documentation
  2. Consider using windows-latest if you want to automatically use the latest supported Windows runner
  3. Set up automated checks (e.g., actionlint) in your CI to catch invalid runner labels early

Also applies to: 271-272

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any other potentially invalid runners in the workflow

# Search for runner specifications in the workflow
echo "Runner specifications found in the workflow:"
rg -A 1 "runs-on:" .github/workflows/test.yml

# Extract and list all matrix OS values
echo -e "\nMatrix OS values found in the workflow:"
rg -A 5 "matrix:" .github/workflows/test.yml | rg "^\s*-\s*\w+"

Length of output: 858

🧰 Tools
🪛 actionlint (1.7.4)

187-187: label "windows-2025" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's false-positive of actionlint. windows-2025 is recently supported.
https://github.blog/changelog/2024-12-19-windows-server-2025-is-now-in-public-preview/

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shogo82148 了解しました。actionlint が最新のパブリックプレビューに追随できておらず、false-positive になっているということですね。特に問題ないようであればそのまま続行でよいかと思います。もし今後 actionlint などのツールで警告を抑制したい場合は、actionlint.yaml などの設定ファイルで無視するルールを追加してみてください。ありがとうございます!


✏️ Learnings added
Learnt from: shogo82148
PR: shogo82148/actions-setup-perl#2039
File: .github/workflows/test.yml:187-187
Timestamp: 2024-12-20T15:00:46.972Z
Learning: "windows-2025" is recognized as a newly introduced GitHub-hosted Windows runner (in public preview) as of 2024-12-19.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

@shogo82148 shogo82148 merged commit 48643ff into main Dec 20, 2024
27 checks passed
@shogo82148 shogo82148 deleted the windows-2025-is-available branch December 20, 2024 15:04
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