# Nushell core team meeting 2024-06-26
## Attendees
- Darren
- Jack
- Devyn
- Storm
- Antoine
- bew
- Andy

## Agenda
- [x] How did the release go? Seen/Heard about any issues?

## Discussed Topics
- Release - not much. maybe something with setup_nu from hustcer's ci app. Not sure. Devyn to look at #help conversation.

- PWD PRs by YizhePKU - Devyn to ping to see if they're still interested.

- extend ++ operator for lists to records
- `record ++ record` is `merge`
- sounds okay

- background jobs? or at least make sure we don't get stuck on Ctrl-Z

- http commands taking pipeline input for the body
- Andy's plugin currently does this
- avoid collecting
- `http post`, `http put`, `http patch` (body only)

- http formats
- `--content-type application/json` is kind of long
- `-t json`? `--json`?
- form data would be nice
- Pipeline metadata mime types? then we could auto-detect

- vendor autoload
- on `main` right now - can load files from the vendor autoload dir
- test this
- they are sorted by filename and loaded

- make_release documentation (README) feedback
- mention that we generally want to wait before merging the version bump and wait-for-nushell-release PRs
- `cargo check` required after bumping version
- don't merge too many PRs at once to avoid CI getting stuck
- maybe the scripts have some issues, not sure (see what Jack said on discord during the release)

- don't add `wait-for-nushell-release` label unless something is approved & ready to go

## Issues
> :bulb: the issues which [needs-core-team-attention](https://github.com/nushell/nushell/labels/needs-core-team-attention)

> :bulb: **Note**
> to list all the PRs currently [opened in `nushell/nushell`](https://github.com/nushell/nushell/pulls):
> ```nu
> gh pr list --json url,number,author,title
> | from json
> | each {|i|
> $"- [($i.number)]\(($i.url)\) ($i.title) \(@($i.author.login)\)"
> }
> | reverse
> | to text
> ```