teal framework Release preparation (part 2)

[donyunardi]

Summary

We have completed the following enhancements

• teal_transform_module #58
• Remove insertUI in the teal::init teal#669

Let's plan for a release of teal framework packages. We will handle teal modules packages release after this.

Release candidate:

• [CRAN Release]: 0.3.0 teal.logger#94
  • teal.logger v0.3.0 (log_shiny_input_changes)
• teal.reporter v0.4.0 (Archiver Module)
• teal.code v0.6.0 (introduce names to qenv)
• teal.widgets v0.5.1 (several bug fixes)
• teal.data v0.7.0 (deprecate datanames)
• teal.slice v0.6.0 (insertUI)
• teal.transform v0.5.1 (minor code update)
• teal v0.16.0 (teal_transform_module, insertUI, decorator)

Blockers

teal.data

• Update Vignette due to datanames updates teal.data#338

teal/teal.slice

• [Feature Request]: Does it make sense to create dataset for a module in a transform module teal#1271
• Move landing popup feature back to the modules argument teal#1310
• [Question]: Should teal codebase use magrittr teal#1268
• Guidelines around lifecycle::badge in teal packages #86

Deprecation activity

• Make sure all CI pipelines are green before release #98
  Make sure all CI pipelines are green before release (i.e. Scheduled pipeline, etc).

Others

• https://github.com/insightsengineering/coredev-tasks/issues/605