-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
upgrade formatters and rlistings #298
Conversation
Signed-off-by: Marcin <[email protected]>
Unit Tests Summary 1 files 19 suites 28s ⏱️ Results for commit ead040f. ♻️ This comment has been updated with latest results. |
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.
Do we really need 0.5.10? It seems formatters 0.5.8 already introduced the fontspec
argument on wrap_txt
that is needed according to the tests: https://diffify.com/R/formatters/0.5.5/0.5.8
dependency test action https://github.com/insightsengineering/teal.reporter/actions/runs/12768063698 |
Signed-off-by: Marcin <[email protected]>
Hey @llrs-roche I think we are dealing with an issue that is on an edge of rlistings and formatters. Both of them have been released recently and I think we need the newest versions of both to get this function to work. I updated the PR with a new version of rlistings as well and I am rerunning the job |
I see that you added rlisting version too.
Triggering a new run |
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.
The new actions still fail with at ⠴ Resolving release version of withr [25/25] ETA: 0s
Yeah but it fails for I was trying to fix the other strategy ( Would you mind accepting? |
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.
Oh, I didn't know that sometimes the release branch is allowed to break. All good then.
@llrs-roche so think about it like that we have released packages: teal.reporter ver 0.3.0 and it's dependency rtables 0.2.0 When rtables gets an improvement to the version 0.2.0.9001 but does not yet gets released, you sometimes need to satisfy new features in teal.reporter and you bump the dependency version to rtables (>= 0.2.0.9001). So now teal.reporter is dependent on the development version of the rtables. However release strategy only checks released packages, and the last released version is 0.2.0 for which teal.reporter breaks. So untill all dependencies are not released, the release strategy will keep breaking. |
There is also one more tests failing on dependency tests due to formatters+rlistings combination