Skip to content

Releases: gadget-inc/ggt

v1.4.1

05 Feb 21:31
4d529c6
Compare
Choose a tag to compare

Patch Changes

  • e3fe0bb: Don't automatically enable source maps

    We introduced --enable-source-maps in v1.4.0 using the following shebang:

    #!/usr/bin/env -S node --enable-source-maps
    

    This change was made so that source maps would be enabled by default when running ggt, giving Gadget employees more information when ggt crashes. However, this has caused some issues with certain environments (e.g. '-S' is not recognized as an internal or external command), so we are reverting this change and will go back to the following shebang:

    #!/usr/bin/env node
    

    If you are running ggt and want source maps enabled, you can still do so by running ggt with the NODE_OPTIONS environment variable set to --enable-source-maps:

    NODE_OPTIONS='--enable-source-maps' ggt
    

v1.4.0

28 Jan 17:48
dc52f5f
Compare
Choose a tag to compare

Minor Changes

  • fcb272f: Add more --env aliases.

    • ggt pull now accepts --from as an alias for --env
    • ggt push now accepts --to as an alias for --env
  • 7da5de8: Allow ggt pull --from=production to pull files from your production environment.

Patch Changes

  • 3f9b60d: Attempt to fix Error: dest already exists. by moving files one at a time to .gadget/backup/.
  • 9aa8657: Enable source maps for better error messages and debugging.

v1.3.3

09 Oct 18:59
3454b56
Compare
Choose a tag to compare

Patch Changes

  • da25b70: Fix the following assertion error from occurring:

    An error occurred while communicating with Gadget
    
    '' == true
    
    If you think this is a bug, click here to create an issue on GitHub.
    

v1.3.2

07 Oct 18:18
94a2141
Compare
Choose a tag to compare

Patch Changes

  • 11eca08: Fix ggt pull --force still asking for confirmation.

v1.3.1

04 Oct 05:28
2bfc996
Compare
Choose a tag to compare

Patch Changes

  • c7cc65e: Make ggt deploy --force skip asking for confirmation to push.

    ggt deploy --force implies that you want to discard any existing changes on the environment you are deploying from, so it should not ask for confirmation to push.

  • b3752b6: Fix ggt push --force still asking for confirmation.

v1.3.0

02 Oct 20:59
22fb731
Compare
Choose a tag to compare

Minor Changes

  • 04fcce2: ggt dev now outputs application logs!

    In our push to make your local development experience as streamlined as possible, we've now included application logs, by default, to output during a sync session!

    CleanShot 2024-10-02 at 16 04 03@2x

    Not only that, as long as your terminal supports linking, traceID(s) are also setup to take you to the editor logs!

    CleanShot 2024-10-02 at 16 10 53

    No worries if the verbose output isn't your thing, we've got you covered:

    • --no-logs - completely turns off this new feature
    • --my-logs - same as the editor logs boolean for only showing my logs/events
    • --log-level - Set the log level for incoming application logs, debug, info, error

    As always any more info can be found through ggt dev --help!

Patch Changes

  • 38210c3: Never ignore .gadget/ directory

    ggt no longer ignores the .gadget/ directory when it is listed in the .ignore file. The .gadget/ directory is managed by ggt and ignoring it causes issues like infinite sync loops.

v1.2.0

05 Sep 15:28
c5977c5
Compare
Choose a tag to compare

Minor Changes

  • 05cc186: ggt deploy will now show a deleted data warning when pushing changes to production that would cause data loss.

    image

v1.1.0

05 Sep 01:54
5efb512
Compare
Choose a tag to compare

Minor Changes

  • 87875c9: Dropped support for downgrading to ggt v0.4.x

    ggt v1.1.x will no longer output a .gadget/sync.json file that is compatible with ggt v0.4.x. This means local directories that are synced with ggt v1.1.x will no longer be able to be synced with ggt v0.4.x. This change was made to simplify and reduce the complexity of the codebase.

Patch Changes

  • e83ea58: Updated app select to show apps grouped by team!

    CleanShot 2024-08-30 at 17 44 39@2x

v1.0.6

26 Jul 23:18
4ae09ad
Compare
Choose a tag to compare

Patch Changes

  • 09c1010: Fix ggt deploy immediately exiting after confirmation.

v1.0.5

25 Jul 14:28
bb84199
Compare
Choose a tag to compare

Patch Changes

  • 18fb3ca: Bump semver from 7.6.2 to 7.6.3
  • c7632e3: Bump @sentry/node from 8.18.0 to 8.19.0
  • 269554f: Bump dayjs from 1.11.11 to 1.11.12
  • 35cfaf7: Bump boxen from 7.1.1 to 8.0.0
  • 1a82708: Bump normalize-package-data from 6.0.0 to 6.0.2
  • 90ba3fd: Bump ws from 8.17.1 to 8.18.0
  • 0063723: Bump @sentry/node from 7.114.0 to 8.17.0
  • dc39c5d: Downgrade execa from 9.3.0 to 8.0.1 to support Node.js 18 versions lower than 18.18.0
  • 557f56b: Use esbuild to bundle, minify, and tree-shake code and dependencies
  • 8d649a1: Bump @sentry/node from 8.17.0 to 8.18.0
  • 72d7d39: Bump graphql from 16.8.2 to 16.9.0
  • 15d1ad9: Bump string-width from 7.1.0 to 7.2.0
  • 7a64bd8: Fixed an issue causing ggt deploy to hang after deploying an app.
  • 323b386: Fixed an issue causing ggt dev to print "Pulled files." when only hidden files were pulled.