v4.7.1

# trigger.dev v4.7.1

## Upgrade

```sh
npx trigger.dev@latest update  # npm
pnpm dlx trigger.dev@latest update  # pnpm
yarn dlx trigger.dev@latest update  # yarn
bunx trigger.dev@latest update  # bun
```

Self-hosted Docker image: [`ghcr.io/triggerdotdev/trigger.dev:v4.7.1`](https://github.com/triggerdotdev/trigger.dev/pkgs/container/trigger.dev/1326227467?tag=v4.7.1)

## Release notes

Read the full release notes: https://trigger.dev/changelog/v4-7-1

## What's changed

## Improvements
- `trigger.dev init` now stops with a clear error when the target directory has no `package.json`, instead of installing packages into a parent project. A custom task directory entered during interactive `init <path>` is now written to `trigger.config.ts` relative to the project directory. ([`9499bd2a8`](https://github.com/triggerdotdev/trigger.dev/commit/9499bd2a8bd297b1f6a6c047e8231501c195300a))

## Server changes

These changes affect the self-hosted Docker image and Trigger.dev Cloud:

- The CLI and MCP authorization page now shows the account and organizations you're granting access to.

## All packages: v4.7.1

@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev

## Contributors

Chris Arderne, github-actions[bot]

**Full changelog**: https://github.com/triggerdotdev/trigger.dev/compare/v4.7.0...v4.7.1