Skip to content

fix(ci): resolve YAML syntax error and benchmark test failure #93

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

Merged
merged 2 commits into from
May 27, 2025

Conversation

sidmohan0
Copy link
Contributor

Fixes GitHub Actions YAML syntax error on line 109 by breaking down complex single-line Python commands into multi-line format and using python3 instead of python for better compatibility.

Changes:

  • Multi-line Python version logic for better readability
  • python3 instead of python for GitHub Actions compatibility
  • Applied to both nightly-release.yml and beta-release.yml
  • No functional changes, same version progression (4.1.1 → 4.2.0)

Impact:

  • Fixes workflow validation errors
  • Enables automated releases to work correctly
  • Zero breaking changes

sidmohan0 added 2 commits May 26, 2025 20:11
- Break down complex single-line Python commands into multi-line format
- Change python to python3 for better compatibility
- Fix GitHub Actions YAML syntax error on line 109 in beta-release.yml
- Apply same fix to nightly-release.yml for consistency
- Ensure proper YAML structure and validation
- Add lazy import function for Span class to handle runtime usage
- Fix NameError in multi-chunk structured output processing
- Maintain TYPE_CHECKING imports for development experience
- All benchmark tests now passing including structured output
- Resolves issue where Span was only available during type checking
@sidmohan0 sidmohan0 changed the title fix(ci): resolve YAML syntax error in beta-release workflow fix(ci): resolve YAML syntax error and benchmark test failure May 27, 2025
@sidmohan0 sidmohan0 merged commit a284272 into dev May 27, 2025
10 of 11 checks passed
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