Skip to content

Commit

Permalink
chore(release): update changelog
Browse files Browse the repository at this point in the history
  • Loading branch information
jtoar committed Feb 29, 2024
1 parent e644ff1 commit 2e0fe5e
Showing 1 changed file with 6 additions and 67 deletions.
73 changes: 6 additions & 67 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,59 +2,6 @@

## Unreleased

- fix(deploy): handle server file (#10061)

This fixes the CLI commands for Coherence and Flightcontrol. For Coherence, it fixes a bug introduced in the last patch where the logic for detecting the server file in the setup command (`yarn rw setup deploy coherence`) was flipped. For Flightcontrol, it updates the setup command (`yarn rw setup deploy flightcontrol`) so that it handles Corepack and updates the corresponding deploy command (`yarn rw deploy flightcontrol`) so that it detects the server file similar to the Coherence fix.

- chore(docs): Add link to SuperTokens auth (#10067)

Add a missing link to the SuperTokens auth page in the docs. @danbtl

- fix(coherence): update setup command to detect server file

The `yarn rw setup deploy coherence` command now detects if your project has the server file and configures the api prod command accordingly:

```yml
# coherence.yml

api:
# ...
prod:
command: ["yarn", "rw", "build", "api", "&&", "yarn", "node", "api/dist/server.js", "--apiRootPath=/api"]
```
- Update jsdoc for ScenarioData type (#29166)
Fix formatting of JSDocs in `scenario.ts`

- fix(render): reduce memory and handle server file

This PR improves Render deploys by reducing memory consumption and fixing it so that it uses the server file if it's present.

Render deploys seems to consistently run out of memory during the data migration step. This step is configurable and its doubtful that every deploy has data migrations to apply, but it's enabled by default so it runs every time. The main issue is that the data migrate functionality is a plugin so a yarn install kicks off in Render's deploy container which must be more memory-constrained than the build container. (Assuming there are two different containers, which seems to be the case.)

Instead of running data migrations, this PR issues a warning that if you want to run data migrations, you need to first add the `@redwoodjs/cli-data-migrate` package as a devDependency:

```
yarn add -D @redwoodjs/cli-data-migrate
```
That way a `yarn install` won't be necessary to run data migrations.
Although this PR fixes Render deploy so that it uses the server file if present, realtime features still don't seem to work. We're still investigating; in the meantime, consider using another provider like Coherence if you're just getting started and want to try out realtime features.
- Update MetaTags to be Metadata in Docs (#10053)
The tutorial still used the `MetaTags` component instead of the newer `Metadata` component that the generator templates use. This PR updates all instances of `MetaTags` with `Metadata`.
- fix(sentry): move templates to the command's directory
Fix for https://community.redwoodjs.com/t/redwood-v7-0-0-upgrade-guide/5713/25. The template files for the sentry setup command weren't moved out of experimental (follow up to https://github.com/redwoodjs/redwood/pull/9830).
## v7.0.0
- See https://github.com/redwoodjs/redwood/releases/tag/v7.0.0 for the release notes and https://community.redwoodjs.com/t/redwood-v7-0-0-upgrade-guide/5713 for the upgrade guide
- fix(deps): update opentelemetry-js monorepo (#10065)

Updates our opentelemetry packages. This is a breaking change for users of
Expand Down Expand Up @@ -105,25 +52,17 @@

Note that this feature is mainly for local scripting. Most deploy providers don't let you upload dotfiles and usually have their own way of determining environments.

- fix(render): reduce memory and handle server file

This PR improves Render deploys by reducing memory consumption and fixing it so that it uses the server file if it's present.
## v7.0.5

Render deploys seems to consistently run out of memory during the data migration step. This step is configurable and its doubtful that every deploy has data migrations to apply, but it's enabled by default so it runs every time. The main issue is that the data migrate functionality is a plugin so a yarn install kicks off in Render's deploy container which must be more memory-constrained than the build container. (Assuming there are two different containers, which seems to be the case.)

Instead of running data migrations, this PR issues a warning that if you want to run data migrations, you need to first add the `@redwoodjs/cli-data-migrate` package as a devDependency:

```
yarn add -D @redwoodjs/cli-data-migrate
```
- See https://github.com/redwoodjs/redwood/releases/tag/v7.0.5

That way a `yarn install` won't be necessary to run data migrations.
## v7.0.4

Although this PR fixes Render deploy so that it uses the server file if present, realtime features still don't seem to work. We're still investigating; in the meantime, consider using another provider like Coherence if you're just getting started and want to try out realtime features.
- See https://github.com/redwoodjs/redwood/releases/tag/v7.0.4

- Update MetaTags to be Metadata in Docs (#10053)
## v7.0.3

The tutorial still used the `MetaTags` component instead of the newer `Metadata` component that the generator templates use. This PR updates all instances of `MetaTags` with `Metadata`.
- See https://github.com/redwoodjs/redwood/releases/tag/v7.0.3

## v7.0.2

Expand Down

0 comments on commit 2e0fe5e

Please sign in to comment.