vbump teal.data

[m7pr]

Bumping teal.data

[m7pr]

Hey @pawelru we vbumped teal.data in here to the newest CRAN released version.
Now I see dependency conflict in staged-r-dependencies scenario dependency installation.
Do you think we should also remove lookup-refs, as we did remove Remotes, if a package depends on a CRAN-released version?

And only bring back Remotes and lookup-refs once the package relies on a development version again?

[m7pr]

I see the same package installation conflicts in

• tmg vbump teal.data teal.modules.general#836
• tmc vbump teal.data teal.modules.clinical#1326

[pawelru]

I can see in the log that there are some conflicting entires that prevents dependency solver to succeed. This is true for all the PRs you referenced. In here it is:

  Remotes:
      insightsengineering/teal.slice
  Config/Needs/DepsBranch:
      insightsengineering/teal.slice@vbump_tealdata@main

[github-actions]

Unit Tests Summary

  1 files   28 suites   10m 43s ⏱️
278 tests 274 ✅ 4 💤 0 ❌
540 runs  536 ✅ 4 💤 0 ❌

Results for commit 8c88637.

♻️ This comment has been updated with latest results.

[github-actions]

Unit Test Performance Difference

Test Suite	$Status$	Time on main	$±Time$	$±Tests$	$±Skipped$	$±Failures$	$±Errors$
module_teal	💔	$129.70$	$+3.16$	$0$	$0$	$0$	$0$

Results for commit 49ac8ce

♻️ This comment has been updated with latest results.

[m7pr]

@pawelru I decided to remove lookup-refs to avoid collision of Remotes fields and DepsDev/DepsBranch.
Still on ie/setup-r-dependencies@v1 job, but at some point we will move to r-lib/actions/setup-r-dependencies@v2 in here insightsengineering/r.pkg.template#274

I also removed lookup-refs in tmg and tmc

insightsengineering/teal.modules.general#836
insightsengineering/teal.modules.clinical#1326