minor updates

Author: wlandau-lilly

.github/workflows/check.yaml

@@ -15,10 +15,10 @@ jobs:
 
     steps:
       - name: Checkout repo
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4.2.2
 
       - name: Setup R
-        uses: r-lib/actions/setup-r@master
+        uses: r-lib/actions/setup-r@v2
 
       - name: Install system requirements
         run: |
@@ -32,7 +32,7 @@ jobs:
         shell: Rscript {0}
 
       - name: Cache R packages
-        uses: actions/cache@v2
+        uses: actions/cache@v4.1.2
         with:
           path: ${{ env.R_LIBS_USER }}
           key: ${{ runner.os }}-${{ hashFiles('.github/R-version') }}-2-${{ hashFiles('.github/depends.Rds') }}
@@ -46,7 +46,7 @@ jobs:
         shell: Rscript {0}
 
       - name: Cache bookdown results
-        uses: actions/cache@v1
+        uses: actions/cache@v4.1.2
         with:
           path: _bookdown_files
           key: bookdown-${{ hashFiles('**/*Rmd') }}

.github/workflows/publish.yaml

@@ -5,7 +5,7 @@ Description: This repository contains the design specification of the 'targets'
   and the orchestration and branching model. The goal is to help developers contribute
   to core elements of the package. Developers are encouraged to to read
   the rendered output at <https://books.ropensci.org/targets-design>.
-Version: 0.8.1.9000
+Version: 1.8.0.9009
 License: MIT + file LICENSE
 URL: https://books.ropensci.org/targets-design,
   https://github.com/ropensci-books/targets-design

DESCRIPTION

@@ -13,10 +13,9 @@ The following classes define specialized objects for the fields of targets.
 * Value
 * Metrics
 * Store
-    * File
+* File
 * Subpipeline
 * Junction
-* Pedigree
 * Cue
 
 Some types of targets need only some of these objects as fields.
@@ -30,7 +29,6 @@ Metrics | ✓ | ✓ | ✓ | | |
 Store | ✓ | ✓ | ✓ | | |
 Subpipeline | ✓ | ✓ | ✓ |  | |
 Junction |  | ✓ |  | | ✓ |
-Pedigree |  |  | ✓ | ✓ | |
 Cue | ✓ | ✓ | ✓ | | |
 Patternview | | | | | ✓ |
 
@@ -84,10 +82,6 @@ A `subpipeline` is not actually a class of its own, it is just a `pipeline` obje
 
 A `junction` serves as a branching specification for patterns and a budding specification for `stems`. It contains the name of the parent pattern or stem, the names of the children (buds or branches), and the names of the dependencies of each bud or branch. The junction is the explicit representation of the user-defined `pattern` argument of `tar_target()` combined with the hashes of the available dependencies.
 
-### Pedigree class
-
-Whereas junctions are branching specifications for stems and patterns, pedigrees are branching specifications for buds and branches. A pedigree has the name of the parent (pattern or stem) the name of the child (bud or branch) and the integer index of the child in the parent's junction.
-
 ### Cue class
 
 A cue object is a collection of rules for deciding whether a target is up to date. `targets` allows the user to activate or suppress some of these rules to change the conditions under which targets rerun.

composition.Rmd

@@ -30,6 +30,8 @@ _targets/ # Configurable with tar_config_set().
 
 The number of files equals the number of targets plus two, which makes projects easier to upload and share among collaborators than `drake`'s `.drake/` cache. (Files in `_targets/scratch/` do not count because they can all be safely deleted after `tar_make()`.) However, these files may still be too large and too numerous for code-specific version control systems like Git. For such projects, it may be more appropriate to share caches through external version-aware platforms such as Dropbox, Microsoft OneDrive, and Google Docs.
 
+The exception to this data structure is content-addressable storage as explained in the documentation of `targets::tar_repository_cas()`.
+
 ## Targets
 
 With the exception of dynamic files, the return value of each target lives in its own file inside `_targets/objects/`. The file name is the name of the target, and there is no file extension. The metadata keeps track of the storage format that governs how to read and write the target's data. The default format is RDS, so if target `x` has no explicit format, then `readRDS("_targets/objects/x")` will read the data. (However, we state this just for the sake of understanding. The recommended way to read data is `tar_read()`, which takes the storage format into account.)
@@ -82,8 +84,10 @@ These fields are pipe-separated in the flat file. Fields `path` and `children` c
 1. The `command` metadata field (the hash of the R command) is different from last time.
 1. The `depend` metadata field (the hash of the immediate upstream dependency targets and global objects) is different from last time.
 1. The storage `format` (user-specified with `tar_target()` or `tar_option_set()`) is different from last time.
+1. The storage `repository`` (user-specified with `tar_target()` or `tar_option_set()`) is different from last time.
 1. The `iteration` method (user-specified with `tar_target()` or `tar_option_set()`) is different from last time.
 1. A target's file (either the one in `_targets/objects/` or a dynamic file) does not exist or changed since last time.
+1. The target-specific random number generator seed is different from last time.
 
 A target's dependencies can include functions, and these functions are tracked for changes using a custom hashing procedure. When a function's hash changes, the function is considered invalidated, and so are any downstream targets with the `depend` cue turned on. The `targets` package computes the hash of a function in the following way.