Releases: fauna/fauna-shell
3.0.0
Highlights
-
Adds support for staged schema changes. A staged schema change lets you change one or more collection schema without index downtime due to index builds.
-
Introduces the following commands to support staged schema changes:
-
Adds the following options to the
fauna schema diff
command:--active
: Shows the diff between the local and remote active schema.--staged
: Shows the diff between the remote active and remote staged schema.--text
: Shows a text diff instead of a semantic diff
-
Adds the
--active
option to thefauna schema pull
command. The option pulls the remote active schema files for the database into the local schema directory. If the database has staged schema,fauna schema pull
pulls the database's staged schema without this option. -
Adds the
--active
option to thefauna schema push
command. The option skips staging the schema and makes the schema active immediately. -
Adds the
--color
and--no-color
options to the following commands. The options let you enable or disable color formatting. Color formatting is enabled by default if the terminal supports it (determined using chalk/supports-color).
Breaking Changes
-
The
fauna schema push
command now defaults to staging schema. -
Changes the
--non-interactive
option to--no-input
(or its-y
alias) for the following commands: -
Changes the
--force
option to--no-input
(or its-y
alias) for thefauna schema push
command. -
Changes the following commands to use semantic diffs by default:
-
If a database has staged schema,
fauna schema diff
now compares the local schema to the database's staged schema by default. If the database has no staged schema,fauna schema diff
compares the local schema to the remote schema by default.
What's Changed
- Add
schema push --stage
by @macmv in #355 - Add
fauna schema status
by @macmv in #356 - Add
fauna schema commit
andabandon
by @macmv in #357 - Add colors by @macmv in #365
- Add
fauna schema pull --staged
by @macmv in #366 - Add
fauna schema diff --active
by @macmv in #367 - Improve
schema
command output by @macmv in #378 - Improve
diff
args by @macmv in #380 - Don't delete
.fsl
files if user rejects confirmation prompt by @echo-bravo-yahoo in #383 - Fix
fauna schema status
when the local files are invalid by @macmv in #388 - Switch
push
to default to a staged push by @macmv in #387 - Update
schema status
msg for staged default by @jrodewig in #391 - Add
fauna schema pull --active
by @macmv in #392 - Simplify flags to
push
anddiff
by @macmv in #394 - Rename
--force
and--non-interactive
to--no-input
by @macmv in #397 - Bump to version 3.0.0 by @macmv in #395
Full Changelog: v2.0.2-release...v3.0.0-release
2.0.2
What's Changed
- update release pipeline to use node 18 by @mwilde345 in #351
- use builtin header for scoped v4 clients by @mwilde345 in #352
- Release version 2.0.2 by @mwilde345 in #353
Full Changelog: v2.0.1-release...v2.0.2-release
2.0.1
What's Changed
- Dependency upgrade: Minimum supported node version v18 by @echo-bravo-yahoo in #345
- v4 temporary header by @mwilde345 in #346
- Release v2.0.0 by @mwilde345 in #348
- update README for development by @echo-bravo-yahoo in #347
- Send Schema body as FormData; Format schema test file by @mwilde345 in #349
- Release: bump version 2.0.1 by @mwilde345 in #350
Full Changelog: v1.3.1_release...v2.0.1-release
1.3.1
What's Changed
- Improve error logging with
shell
andeval
when connecting to a Fauna client in v4 or v10 - Improved error handling within
eval
- Update README with required Node Version
Full Changelog: v1.3.0...v1.3.1_release
1.3.0
What's Changed
- Move
project
andenvironment
commands from beta to GA - Add upgrade instructions to the README
Full Changelog: 1.2.1...v1.3.0
1.2.1
What's Changed
- Improve error handling in the shell.
- Default the
.fauna-shell
file to read-only permissions (0600), as it contains fauna secrets. - Fix examples in
fauna endpoint add
. - Fix a bug where timeout was not passed to the fauna client correctly.
Full Changelog: 1.2.0...1.2.1
1.2.0
What's Changed
- Add project configuration. Projects can be created, which makes a
.fauna-project
file that should get checked in to VCS. These projects can be used to deploy schema changes and share project settings more easily. - The format of
.fauna-shell
has been updated, to support adding more fields later. All endpoints now live under aendpoint
object, as opposed to being a top-level field. Files will be migrated if modified by the shell, and the shell can still parse the old format as well. fauna cloud-login
no longer conflicts with your session in the dashboard, so it can be used to log in on both the website and shell.- Renamed
fauna add-endpoint
and similar tofauna endpoint add
, and improved these commands to be available without user interaction.
For developers
Internally, we switched a lot of code over to typescript. This was just to help develop new functionality.
Full Changelog: 1.1.0...1.2.0
1.1.2
- Fix bug with scoped database queries. Ensure
ensureDbScopeClient
passes along version flag.
Full Changelog: 1.1.1...1.1.2
1.1.1
- Fix errors being output by the
cloud-login
command.
Full Changelog: 1.1.0...1.1.1
1.2.0-beta1
What's Changed
- Add project configuration, which is managed with
fauna project
andfauna stack
. - Update
fauna cloud-login
to keep a valid session alive. - Cleanup unused flags on a number of commands (namely
--graphqlHost
and--graphqlPort
). - Add
--endpointURL
, and deprecate the--domain
,--scheme
, and--port
flags.
Full Changelog: 1.1.0...1.2.0-beta1