Skip to content

Releases: redwoodjs/redwood

v0.6.0

23 Apr 03:57
Compare
Choose a tag to compare

Along with bug fixes, ENV var support, Router enhancements, and improved TypeScript support, this release introduces a new workflow with CLI tools for contributing to the RedwoodJS Framework. For more information, please read CONTRIBUTING.md 🤩

Changed

  • Prisma: upgrade to Prisma-2.0.0-beta.3 #457
  • Config: Only use redwood-eslint-plugin when in a redwood project #443
  • Framework: build core packages and reference them correctly #456
  • TypeScript: Let api-dev-server and webpack load .ts and .tsx files #438

Added

  • CLI: Add workflow tools for local development #429 #442
    • split rwdev watch into copy and copy:watch #445 @jtoar
    • fix build:watch scripts and own add own resolve function #455
    • edit CONTRIBUTING.md #435 @jtoar
  • Config: support ENV vars in webpack projects #430 @snormore
    • write tests and docs for environmental variables #444
  • Router: add useMatch for crafting stateful links #416 @RobertBroersma
  • TypeScript: Setup TS Project References #359 @mohsen1
  • CLI: add 'yarn rw upgrade' helper to upgrade @redwoodjs packages #436

Fixed

  • Router: fixes validatePath duplicate params & reject spaces in routes #420 @olance
  • Deploy: add process.exit(1) to ensure Netlify build fails on error #447
  • CLI: fixes mutation constant names in generated code #458
  • Docs: fix link markup #459 @benmccann

Breaking ⚠️

Breaking changes only apply to Apps upgrading from previous versions.

Prisma-2.0.0-beta.3 has two major changes that may affect some applications upgrading from previous Redwood versions.

  • Enums are now disallowed for SQLite
  • Required 1-1 self relations are forbidden now

Release notes are available here.


How to upgrade RedwoodJS packages to v0.6.0

Redwood v0.6.0 includes a new CLI command to upgrade @redwoodjs NPM packages. However, you must first upgrade to v0.6.0 to use yarn rw upgrade

Update your @redwoodjs/* packages.

Four packages should be updated to v0.6.0

Root directory package.json

  • "@redwoodjs/core": "^0.6.0”

web/package.json

  • "@redwoodjs/web": "^0.6.0”
  • "@redwoodjs/router": "^0.6.0”

api/package.json

  • "@redwoodjs/api": "^0.6.0”

After updating and saving the files, install the packages from the root directory:
$ yarn install

v0.6.0-rc.2

22 Apr 19:33
Compare
Choose a tag to compare
v0.6.0-rc.2 Pre-release
Pre-release
v0.6.0-rc.2

v0.6.0-rc.1

18 Apr 19:36
Compare
Choose a tag to compare
v0.6.0-rc.1 Pre-release
Pre-release
v0.6.0-rc.1

v0.5.0

15 Apr 02:56
Compare
Choose a tag to compare

This release includes Prisma-2.0.0-beta.2, which is a big update that has many improvements, bug fixes, and new features. 🚀Prisma introduced a new relation syntax and support, which allows for complex relationships within `schema.prisma' models. RedwoodJS has improved its generators to support many model relations' use-cases. However, there are generator support limitations, which you can read about here on our community Forum. 👈

Additionally, Redwood now has a Netlify Plugin to set the DB provider during deployment. See the section below "Using the New Netlify Provider Plugin" for more information.

Changed

Added

Fixed

  • Router rendering bug #380
  • Windows support for redwoodjs/redwood build scripts #363
  • Windows support for create-redwood-app build scripts #410
  • Redwood Router: fix route matching by enforcing type constraints #353 @olance
  • Redwood Forms: fix setState warning from setError call #411 @dominicchapman

Breaking ⚠️

This breaking change only applies to Apps upgrading from previous versions.

Migration files from previous Prisma versions are incompatible with prisma-2.0.0-beta.2. This means new local and deploy migrations will likely fail for Apps upgrading. Workaround:

  1. Remove the migration directory and files (delete api/prisma/migrations directory) and then re-create using yarn rw db save
  2. If that doesn't resolve the issue, then delete the contents of the deployed DB _Migration table (if applicable)

Using the New Netlify Provider Plugin (optional)

These steps only apply to Apps upgrading from previous versions. New Apps already include these changes.

Redwood apps running any version can use the Netlify Provider plugin, which eliminates workarounds required to use ’SQLite’ for local development and ‘PostgreSQL’ (or other DBs) for production deployment.

If you are using PostgreSQL in production, follow the steps below.

If you need to customize your DB provider (to use MySQL, for example), refer to documentation for 'netlify-plugin-prisma-provider’. Changing the provider is as simple as adding a new environment variable in Netlify.

Add the plugin package to your App

Redwood uses yarn workspaces. Run this command to add the package to the root package.json.
yarn add -W netlify-plugin-prisma-provider

Update Netlify deployment settings

Add the following configuration to your App’s netlify.toml:

[[plugins]]
package = 'netlify-plugin-prisma-provider'
  [plugins.inputs]
  path = 'api/prisma/schema.prisma'

How to upgrade RedwoodJS packages to v0.5.0

Update your @redwoodjs/* packages.

Four packages should be updated to v0.5.0

Root directory package.json

  • "@redwoodjs/core": "^0.5.0”

web/package.json

  • "@redwoodjs/web": "^0.5.0”
  • "@redwoodjs/router": "^0.5.0”

api/package.json

  • "@redwoodjs/api": "^0.5.0”

After updating and saving the files, install the packages from the root directory:
$ yarn install

v0.4.0

01 Apr 22:45
Compare
Choose a tag to compare

Changed

Added

Fixed

  • Fixed a problem with the Router where it would try to render a Page without the correct params. #380

How to upgrade to v0.4.0*

Update your @redwoodjs/* packages.

Four packages should be updated to v0.4.0

Root directory package.json

  • "@redwoodjs/core": "^0.4.0”

web/package.json

  • "@redwoodjs/web": "^0.4.0”
  • "@redwoodjs/router": "^0.4.0”

api/package.json

  • "@redwoodjs/api": "^0.4.0”

After updating and saving the files, install the packages from the root directory:
$ yarn install

v0.3.2

26 Mar 00:16
Compare
Choose a tag to compare

⚠️ This release includes a breaking change where we no longer import db automatically (#334). See "How to upgrade to v0.3.2" for more information. ⚠️

Changed

  • Do not import db automatically. #334

Added

  • new command yarn rw info to get system environment #329
  • create redwood-app can be instantiated in an empty directory #315 @olance
  • Prisma is updated to preview24 #303
  • Added a way to change the webpack configuration #312 @Idered

Fixed

  • Fix Netlify deploy issue with src path #338
  • Fix scaffold and sdl generator `Routes.js’ insertion order #336
  • Fix yarn rw test #290
  • Change the way that routes are matched so that it works in Firefox #308
  • Fix ‘yarn rw help’ issue with output on Windows #331

👉 How to upgrade to v0.3.2

(1 of 3) Create a new folder and file api/src/lib/db.js

This adds a way to instantiate the database.

  • create api/src/lib/db.js file
  • copy and paste the following into db.js
// See https://github.com/prisma/prisma2/blob/master/docs/prisma-client-js/api.md#constructor
// for options.

import { PrismaClient } from '@prisma/client'

export const db = new PrismaClient()

(2 of 3) Manually update Files

First, add an import and update the export in your api/src/functions/graphql.js file.

See this example of the updated template file.

  • Add this line to your list of imports:
import { db } from 'src/lib/db'
  • Export db in export const handler = createGraphQLHandler({...}). Add this to the end of the export after schema: makeMergedSchema({...}) (approx. line 18):
db,

Secondly, for each Services file within api/src/services/*, do the following:

  • add this line at the top:
// api/src/services/*
import { db } from 'src/lib/db'

For example, if you completed the RedwoodJS Tutorial you would have posts.js and contacts.js within api/src/services/posts/ and api/src/services/contacts/, respectively. You would add the import statement to the top of each of those files.

(3 of 3) Update your @redwoodjs/* packages.

Four packages should be updated to v0.3.2

Root directory package.json

  • "@redwoodjs/core": "^0.3.2”

web/package.json

  • "@redwoodjs/web": "^0.3.2”
  • "@redwoodjs/router": "^0.3.2”

api/package.json

  • "@redwoodjs/api": "^0.3.2”

After updating and saving the files, install the packages from the root directory:
$ yarn install

v0.3.1

25 Mar 23:48
Compare
Choose a tag to compare

v0.3.0

25 Mar 21:53
Compare
Choose a tag to compare

v0.2.5

18 Mar 01:00
Compare
Choose a tag to compare

Fixed

Items below include changes from v0.2.3 and v0.2.4

  • Windows fix Cell regex issue #276
  • Pass resolver info object to services e842179
  • misc bug fixes and repo-specific CI improvements to tests and linter #247 #257 #262 #274
  • return RWJS version in GraphQL query #255 | kudos @AryanJ-NYC
  • improve README with links and fixes #266 | kudos @Thieffen
  • security warning fix #274

How to Upgrade your RedwoodJS App

File Changes

You will need to replicate changes to three files shown in redwoodjs/create-redwood-app/#39

  1. .env
  2. .env.defaults
  3. api/prisma/schema.prisma

Package Updates

Four packages should be updated to v0.2.5

Root directory package.json

  • "@redwoodjs/core": "^0.2.5”
    web/package.json
  • "@redwoodjs/web": "^0.2.5”
  • "@redwoodjs/router": "^0.2.5”
    api/package.json
  • "@redwoodjs/api": "^0.2.5”

After updating and saving the files, install the packages from the root directory:
$ yarn install

v0.2.2

14 Mar 21:55
Compare
Choose a tag to compare

Fixed

How to Upgrade your RedwoodJS App

Four packages should be updated to v0.2.2:

Root directory package.json

  • "@redwoodjs/core": "^0.2.2”
    web/package.json
  • "@redwoodjs/web": "^0.2.2”
  • "@redwoodjs/router": "^0.2.2”
    api/package.json
  • "@redwoodjs/api": "^0.2.2”

Once you’ve changed and saved the files, run yarn install from root directory.