# 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.
