- 
                Notifications
    
You must be signed in to change notification settings  - Fork 85
 
add 1.2.2 to bun-version matrix at workflows #1643
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
Conversation
| 
           Thanks @kravetsone Could you please check whether that works with the existing benchmark frontend (having two minor bun versions): 
 As far as I am aware of, it is only able to fetch a single unique major version for each runtime. For Node that was was always sufficient. No Idea how to fix this quickly though. Instead of  A quick workaround could be maybe to only benchmark bun 1.2?  | 
    
          
 As hack we can probably use minor version as major for Bun here 
 Potentially can solve it (but I can't check now)  | 
    
| 
           I don't think we need to leave tests for  IMO bun is fast changing and still in heavy development process, and I think most of the user immediately update to the newest version, especially with how easy it is with   | 
    
| 
           @kravetsone could you change it?  | 
    
          
 Okay!  | 
    
| 
           Can we check this logic? 
 Sorry huh but i make workaround for bun to include Major.Minor in versioning  | 
    
| throw new Error('Could not get dirname'); | ||
| } | ||
| 
               | 
          ||
| function getRuntimeWithVersion() { | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I implement this
because determine runtime by USER env is bad practic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
before this npm run start:bun will generate results for node@22 (but its Bun results)
| 
           Linting errors  | 
    
| 
           oh sorry forgot about it  | 
    
| 
           idk how to run lint command here lol its just return  | 
    
| 
           It's because of line ending https://stackoverflow.com/questions/1552749/difference-between-cr-lf-lf-and-cr-line-break-types run   | 
    
          
 Yeah i know about this Can anyone fix linter issue? Sorry for this)  | 
    
          
 I can run   | 
    
          
 mhh that's weird, have you tried running prettier? that should normalize newlines to  
 Yeah if the above doesn't work I can fix it for you.  | 
    
          
 can u approve CI again? Looks like there not formatting error but when i run prettier -w or eslint fixes it just do that boring tooling(  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good now (no linting errors any more), albeit a bit hacky 😁. What do you think @DarkGL ?
| 
           lgtm  | 
    
          
 No that is a bug. Can you reproduce it locally and find its cause?  | 
    
          
 Maybe this happends just because site deployed before Action with build runs As for now it works fine  | 
    
          
 Oh right 😅 that could be it. But now the frontend only lists Bun 1.2, not 1.1. The latter is missing from   | 
    
          
 Yeah i forgot about it and later open this pr  | 
    


Description
Just add bun version from new major to CI matrix
Testing
CI
Checklist