# lifecycle 1.0.3
* The `with` line is now an info bullet. The `details` lines are info
bullets by default, unless the argument is named.
* Indirect usages of deprecated features now mention the package that
likely used the deprecated feature and recommends contacting the
authors (#135).
* Indirect usages of `deprecate_warn()` no longer warn repeatedly,
even if `always = TRUE` (#135).
* In tests, `deprecate_soft()` will only warn if the deprecated function
is called directly from the package being tested, not one of its dependencies.
This ensures that you only see the warning when it's your responsibility to
do something about it (#134).
* Soft deprecations now only warn every 8 hours in non-package code (#134).
# lifecycle 1.0.2
* You can now generate arbitrary text in a deprecation message by
wrapping `what` or `with` in `I()` (#120).
* `deprecate_warn()` gains an `always = TRUE` argument to force
warnings to occur every time, not every 8 hours. This adds an extra
step in between `deprecate_warn()` and `deprecate_stop()` (#124).
* `signal_stage()` now supports `with` (#116).
# lifecycle 1.0.1
* `deprecate_soft()` now follows the verbosity option when called from
the global environment (#113).
* `last_warnings()` has been renamed to `last_lifecycle_warnings()`
and `last_warning()` has been removed. This is for compatibility
with the future `rlang::last_warnings()` function to be released in
the next rlang version.
All checksums have been double-checked against existing RMD160 and
SHA512 hashes
Could not be committed due to merge conflict:
devel/py-traitlets/distinfo
The following distfiles were unfetchable (note: some may be only fetched
conditionally):
./devel/pvs/distinfo pvs-3.2-solaris.tgz
./devel/eclipse/distinfo eclipse-sourceBuild-srcIncluded-3.0.1.zip
# lifecycle 1.0.0
* New vignettes:
* `vignette("stages")` describes the lifecycle stages
* `vignette("manage")` teaches you how to manage lifecycle changes in
functions you _use_.
* `vignette("communicate")` shows how to use lifecycle in functions that
you _write_.
* In `deprecate_soft()`, `deprecate_warn()`, and `deprecate_stop()`:
* You can deprecate an argument with `foo(arg)` instead of `foo(arg =)` (#78).
This syntax is similar in spirit to the formal arguments of function
definitions.
* You can deprecate R6 methods by using `class$method()` (#54).
* A character vector `details` is now converted into a bulleted list (#55).
* Messages for non-prefix functions (like "`x<-`()" and "`%>%`()")
look a little nicer (#95).
* Manually printed warnings now omit the advice footer (#68).
* Experimental `signal_stage()` can be used to signal that a function is
experimental or superseded. These signals are not currently hooked up to any
behaviour, but we'll add tools in a future release (#44).
* `lifecycle_cnd_data()` has been removed; as far as I can tell it wasn't
used by anyone.
Manage the life cycle of your exported functions with shared
conventions, documentation badges, and non-invasive deprecation
warnings. The 'lifecycle' package defines four development stages
(experimental, maturing, stable, and questioning) and three
deprecation stages (soft-deprecated, deprecated, and defunct). It
makes it easy to insert badges corresponding to these stages in your
documentation. Usage of deprecated functions are signalled with
increasing levels of non-invasive verbosity.
