Skip to contents

Changelog

Source: NEWS.md

tarchetypes 0.13.2.9002 (development)

  • Try different paths to look for output files in tar_quarto_rep() (#217). Hard to tell if Quarto uses the current working directory or the directory of the source file as the destination for the output, and their policy may have changed in a different version of Quarto.
  • Add tar_tangle() (#226).

tarchetypes 0.13.2

CRAN release: 2025-09-13

tarchetypes 0.13.1

CRAN release: 2025-05-08

  • Restore custom output files in tar_quarto_rep() (#217, @arcruz0). For #211, users should write relative paths to output files in the output_file column of execute_params, and they should avoid writing a _quarto.yml with an output-dir field.
  • Set deployment = targets::tar_option_get("deployment") in tar_render() and tar_quarto().
  • Set cli.num_colors = 1L and cli.dynamic = FALSE in R Markdown target factories.

tarchetypes 0.13.0

CRAN release: 2025-04-10

tarchetypes 0.12.0

CRAN release: 2025-01-31

tarchetypes 0.11.0

CRAN release: 2024-11-15

tarchetypes 0.10.0

CRAN release: 2024-09-26

tarchetypes 0.9.0

CRAN release: 2024-04-17

Invalidating changes

tarchetypes 0.8.0

CRAN release: 2024-03-18

  • Expose the new description argument of tar_target() in targets 1.5.1.9001.
  • tar_map() and other static branching target factories now append values to the target descriptions. Use the descriptions argument of those functions to customize.
  • Ensure consistent repository settings in tar_change() and tar_map_rep().
  • tar_knit(), tar_render(), tar_quarto(), and their “rep” and “raw” versions all gain a working_directory argument to change the working directory the report knits from. Users who set working_directory need to supply the store argument of tar_load() and tar_read() relative to the working directory so the report knows where to find the data (#169).
  • tar_knit(), tar_render(), tar_quarto(), and their “raw” versions all gain an output_file argument to more conveniently set the file path to the rendered output file.
  • tar_quarto() and its “rep” and “raw” versions all gain a new quarto_args argument for advanced Quarto arguments (#166, @petrbouchal).

tarchetypes 0.7.12

CRAN release: 2024-02-06

  • Adjust tests because group iteration is now explicitly prohibited for dynamic targets.

tarchetypes 0.7.11

CRAN release: 2024-01-09

tarchetypes 0.7.10

CRAN release: 2023-12-04

  • Prepare to use tar_seed_create() and tar_seed_set() (https://github.com/ropensci/targets/issues/1139). Future versions of tarchetypes should use these package functions, but this version cannot because of the compatibility constraints of the release cycle.
  • Migrate tests to targets >= 1.3.2.9004 progress statuses (“completed” instead of “built”, “dispatched” instead of “started”).

tarchetypes 0.7.9

CRAN release: 2023-10-04

tarchetypes 0.7.8

CRAN release: 2023-09-01

  • Relax overly strict assertion on R Markdown / Quarto parameter lists (@rmgpanw, #152).
  • Adjust a test to comply with upcoming targets 1.3.0.

tarchetypes 0.7.7

CRAN release: 2023-06-15

  • Allow format = "file_fast" in target factories.

tarchetypes 0.7.6

CRAN release: 2023-05-02

  • Support Quarto profiles through the QUARTO_PROFILE environment variable (#139, @andrewheiss).
  • Take the basename of the source file for #129 so the output files land correctly when the source file is in a subdirectory (#129, targets issue 1047, @joelnitta).
  • Use targets::tar_runtime_object()$store instead of targets::tar_runtime_object()$get_store() to ensure forward compatibility with targets.
  • Use interactive test for tar_download() to avoid unpredictable network issues outside our control.

tarchetypes 0.7.5

CRAN release: 2023-03-07

tarchetypes 0.7.4

CRAN release: 2023-01-06

  • Implement rep_workers to control inner parallelism in batched replication functions (#117).
  • Ensure the function passed to furrr functions has environment tar_option_get("envir").
  • Allow subdirectories of rendered reports with tar_quarto_rep() (#129, @mglev1n).

tarchetypes 0.7.3

CRAN release: 2022-11-29

  • Support nested futures for parallelism among reps within batches (#117, @kkmann).
  • Add Quarto troubleshooting section to help files.

tarchetypes 0.7.2

CRAN release: 2022-10-31

tarchetypes 0.7.1

CRAN release: 2022-09-07

tarchetypes 0.7.0

CRAN release: 2022-08-05

  • Add new functions tar_quarto() and tar_quarto_rep() (and “raw” versions) for Quarto documents and projects in pipelines (#89).
  • Add new function tar_quarto_files() to inspect Quarto projects and documents for important files: source files to inspect for target dependencies, output documents, and Quarto-specific inputs like _quarto.yml. Uses quarto::quarto_inspect() and powers the automatic file detection in tar_quarto() etc. (#89).
  • Add runtime guardrails to the params argument of tar_render_rep() (must be a data frame with unique rows (or unique elements of output_file)).
  • Temporarily change root.dir when scanning for dependencies so knitr child documents work (#93, @mutlusun).
  • Use format = "rds" for target_batch in tar_map_rep_raw() so the global format option does not mess up the pipeline.
  • Handle non-atomic length-one list columns in tar_append_static_values().
  • Allow tar_render() to work with just one row of parameters (#96, #97, @ugoebel73).
  • Remove dependencies and collect garbage before running reports.
  • Make sure all the target factories have memory and garbage_collection arguments.

tarchetypes 0.6.0

CRAN release: 2022-04-19

tarchetypes 0.4.1

CRAN release: 2022-01-07

  • Select list elements from command1 using [[ and not [ in tar_map2() functions.

tarchetypes 0.4.0

CRAN release: 2021-12-10

tarchetypes 0.3.2

CRAN release: 2021-10-26

tarchetypes 0.3.1

CRAN release: 2021-09-21

  • Relax assertion on language objects.
  • Explain targets timestamps correctly in the help files of tar_age() and tar_cue_age().

tarchetypes 0.3.0

CRAN release: 2021-08-04

Invalidating changes

  • When names = NULL in tar_map(), use hashes instead of numeric indexes for generated target names (#67). That way, target names are no longer sensitive to the order of values, and so targets will incorrectly invalidate less often. Unfortunately, this is an invalidating change: some targets will automatically rerun after you install this version of tarchetypes. I apologize for the inconvenience this causes. However, we do need this patch in order to solve #67, and targets will incorrectly invalidate less frequently in the future.

Enhancements

  • Migrate to utilities for error handling and metaprogramming exported from targets (#59).

tarchetypes 0.2.1

CRAN release: 2021-06-21

Bug fixes

  • Make the *_raw() target factories process command the same way whether it is an expression or ordinary language object.
  • Ensure compatibility with targets 0.5.0.9000, which logs skipped targets.

New features

tarchetypes 0.2.0

CRAN release: 2021-05-11

tarchetypes 0.1.1

CRAN release: 2021-03-28

  • Unset crayon.enabled for literate programming.
  • Switch meaning of %||% and %|||% to conform to historical precedent.

tarchetypes 0.1.0

CRAN release: 2021-02-27

tarchetypes 0.0.4

CRAN release: 2021-02-02

  • Skip literate programming tests if pandoc is missing or has an insufficient version.
  • Use explicit temp files in examples even when running inside targets::tar_dir(). (targets::tar_dir() and targets::tar_test() already run code in a temporary directory.)
  • Add comments in the examples to emphasize that targets::tar_dir() runs code in a temporary directory, which means all ostensibly files created in the enclosed expression will actually be written to temporary storage and not the user’s file space.

tarchetypes 0.0.2

CRAN release: 2021-02-01

  • Make sure every function with a help file in man/ has Rd-tags \value and \arguments.
  • For every function with a help file in man/, describe the return value in the \value Rd tag. For each function that returns a target definition object or list of target definition objects, the \value tag now links to https://books.ropensci.org/targets/, the user manual where the purpose of target definition objects is explained, and https://books.ropensci.org/targets-design/, the design specification which documents the structure and composition of target definition objects.
  • Ensure that examples, vignettes, and test do not write to the home file space of the user.
  • Ensure that no function defined in the tarchetypes package writes by default to the home file space of the user. The paths of all output files are controlled by non-tarchetypes functions that invoke tarchetypes.

tarchetypes 0.0.1

tarchetypes 0.0.0.9000