cargo install nu --no-default-features
```

# Introducing: stable and unstable features

Another part of the current refactor work is that we're splitting the "stable" and "unstable" features up. This lets us experiment a bit easier before a command becomes a stable part of the releases.

Now, to install all the stable features, you can use:

```
cargo install nu --features=stable
```

If you want to get both stable _and_ unstable features, use:

```
cargo install nu --all-features
```

Warning: unless you're working on Nu itself you may not want to install all features currently, as you'll see that we're working on an internal tracing tool.

# Moving the book(s) (sebastian-xyz)

We've been hard at working building up the websites. In the previous release, we talked about "nushell.sh" and the new website there. Since then, we've consolidated the books into the new website. Please update your book links to point to the new site:

- Nu book - [nushell.sh/book](https://www.nushell.sh/book/)
- Contributor book - [nushell.sh/contributor-book](https://www.nushell.sh/contributor-book/)
- Cookbook (in-progress) - [nushell.sh/cookbook](https://www.nushell.sh/cookbook/)

# Command improvements

## Embed -> Wrap (sophiajt, andrasio)

For better readability, we've renamed the `embed` command to `wrap`. As the name implies, you can now `wrap` one table with another. You can also use `wrap` to create a table from a stream of values.

For example, you may have a list of strings you want to turn into a table:

```
> ls | get name
────┬────────────────────
 #  │ <value>
────┼────────────────────
  0 │ target
  1 │ CODE_OF_CONDUCT.md
  2 │ .cargo
  3 │ src
  4 │ features.toml
  5 │ TODO.md
```

We can now name this table using `wrap`:

```
> ls | get name | wrap filename
────┬────────────────────
 #  │ filename
────┼────────────────────
  0 │ target
  1 │ CODE_OF_CONDUCT.md
  2 │ .cargo
  3 │ src
  4 │ features.toml
  5 │ TODO.md
```

# Internal improvements (wycats, sophiajt, thibran, thegedge)

Though not visible as additional new features, a group of us has been at work refactoring and cleaning up Nu's internals. This should help us both fix some long-standing bugs as well as make way for new features in the future.

We've also internally introduced a new "line" type, which represents strings that carry a line ending with them. This helps us more easily traffic string data through the system and know how best to output it at the end of the pipeline.

# Bugfixes

Of course, with each release, there are the usual bugfixes. We've improved tilde expansion (naufraghi), how internal pipelines are handled (thegedge), and more.

# Improved docs (tchak, coolshaurya, sebastian-xyz)

A big "thank you!" for folks continuing to work on the on-going command documentation efforts. Already, we're seeing people [read about the commands](/book/command_reference.html) on the new website to help them learn Nu, which is great!

# What's next?

You might have noticed that with 0.7.0, we're seemingly getting close to 1.0. What happens after 0.9.0? Are we going to take the leap?

In short, not just yet. After 0.9.0, we'll release 0.10.0. Nu is maturing, but it isn't quite ready for the big One-Point-Oh. We'll continue maturing it until it's ready to make the move.