chore: Add nu 0.108 to test matrix - #182

Walkthrough

Version bump from Nu 0.106.0 to 0.108.0 across GitHub Actions workflows and README documentation. Updated matrix definitions in four workflow files and corresponding examples in English and Chinese README files.

Changes

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

This change consists of homogeneous, repetitive version updates with no logic modifications. All edits follow the same pattern across files.

Possibly related PRs

• chore: Update Nu version in workflows and README files to 0.103 #139: Updates workflows and README files with Nushell version bumps, following the same pattern but targeting a different version.
• feat: Add latest-matrix.yaml workflow to test latest Nu on various platforms #135: Introduced the latest-matrix.yaml workflow file that is now being updated in this PR.

Poem

🐰 A new Nu version hops in with glee,
From 0.106 to 0.108—fresh as can be!
Workflows and docs aligned just right,
Testing matrices shine, testing bright! 🌟

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Code Analysis

• Version updates from 0.106.0 to 0.108.0 across GitHub Actions workflows
• Documentation updates in README files to reflect new version
• Consistent version bump across multiple workflow files
• Maintains backward compatibility by keeping older versions in test matrices

Security Review

• No frontend security vulnerabilities detected in this infrastructure code
• GitHub Actions workflows appear to follow standard security practices
• No sensitive data exposure or XSS risks in the provided changes

Optimization Suggestions

• Consider implementing caching strategies for GitHub Actions to improve CI/CD performance
• Evaluate if all older versions in the test matrix are still necessary to optimize test execution time
• Consider using version ranges or latest stable tags for more flexible version management

Overall Quality: 4

Note: This review focuses on infrastructure/CI configuration changes rather than frontend application code. The changes appear to be routine version updates with proper maintenance of backward compatibility.