Automate CLI releases.

.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets)
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.changeset/config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.0.5/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "restricted",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

.changeset/forty-seas-pull.md

@@ -0,0 +1,7 @@
+---
+"fauna-shell": patch
+---
+
+Redact secrets in verbose logging.
+
+With verbose logging enabled, the CLI previously logged the full resolved CLI config, which could inadvertently expose account keys and secrets stored in a config file. The CLI masks sensitive information, such as account keys and secrets, when logging details from arguments, flags, or environment variables. This change updates verbose logging to redact account keys and secrets logged from config files.

.changeset/lovely-suns-suffer.md

@@ -0,0 +1,7 @@
+---
+"fauna-shell": patch
+---
+
+Fix incorrect minimum Node.js version
+
+The documentation and package.json's "engines" field previously stated that the CLI could be run with Node.js 20.x.x or later. However, the CLI uses APIs, such as the single-executable application (SEA) API, that aren't available until Node.js 20.18.x. This change updates the documentation, the "engines" field of package.json, and the test runner to test against Node.js 20.18.x to prevent further backward-incompatible changes.

.changeset/modern-garlics-fetch.md

@@ -0,0 +1,15 @@
+---
+"fauna-shell": patch
+---
+
+Remove the `--json` flag from commands that don't support it.
+
+The `--json` flag was implemented as a top-level option, implying it could be used with all commands. However, it only has an effect for a subset of commands. After this change, only the following commands support the `--json` flag:
+
+- database create
+- database list
+- export get
+- export create
+- export list
+- query
+- shell

.changeset/small-mugs-drum.md

@@ -0,0 +1,8 @@
+---
+"fauna-shell": patch
+---
+
+Improve the export user experience.
+
+- `fauna export create` allows you to provide a target S3 URI with the `--destination` flag. Previously, you had to provide both the `--bucket` and `--path` separately.
+- `fauna export create` now supports custom idempotency tokens with the `--idempotency` flag. You can use the flag to retry requests without triggering duplicate exports.

.changeset/sour-zoos-sniff.md

@@ -0,0 +1,7 @@
+---
+"fauna-shell": patch
+---
+
+Add retry options for queries.
+
+The `fauna query` and `fauna shell` commands now support retry flags for throttling and contended transactions. For FQL v10 queries, the following flags are supported: `--max-attempts`, `--max-backoff`, and `--max-contention-retries`. For FQL v4 queries, only `--max-contention-retries` is supported.

.github/workflows/release.yml

@@ -0,0 +1,63 @@
+name: NPM Release
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - "package.json"
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          # we need two commits
+          fetch-depth: 2
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: "lts/*"
+          registry-url: "https://registry.npmjs.org"
+
+      - name: Check version
+        id: check_version
+        run: ./scripts/check-version.js
+
+      # - name: Generate Release Notes
+      #   if: steps.check_version.outputs.do_publish == 'true'
+      #   run: |
+      #     if [ -f "RELEASE_NOTES.md" ] && grep -q "## \[${{ steps.check_version.outputs.new_version }}\]" RELEASE_NOTES.md; then
+      #       sed -n "/## \[${{ steps.check_version.outputs.new_version }}\]/,/## \[/p" RELEASE_NOTES.md | sed '$d' > release_body.md
+      #     else
+      #       echo "### Automated Release Notes" > release_body.md
+      #       echo "" >> release_body.md
+      #       echo "#### Changes" >> release_body.md
+      #       git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:"- %s" >> release_body.md
+      #     fi
+
+      - name: Create Git Tag
+        if: steps.check_version.outputs.do_publish == 'true'
+        run: |
+          git config user.name github-actions
+          git config user.email github-actions@github.com
+          git tag v${{ steps.check_version.outputs.new_version }}
+          git push origin v${{ steps.check_version.outputs.new_version }}
+
+      - name: Publish to NPM
+        if: steps.check_version.outputs.do_publish == 'true'
+        run: npm publish --dry-run
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+      - name: Create GitHub Release
+        if: steps.check_version.outputs.do_publish == 'true'
+        uses: actions/create-release@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          tag_name: v${{ steps.check_version.outputs.new_version }}
+          release_name: Release ${{ steps.check_version.outputs.new_version }}
+          body_path: release_body.md