chore: version packages (#614)

This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @gram-ai/[email protected]

### Patch Changes

- a8cc73e: Ensure .gitignore is scaffolded out with templating Gram
Functions projects.

## @gram-ai/[email protected]

### Patch Changes

- 676405c: Updated the `manifest()` method of the Gram Functions TS
framework to avoid
JSON-serializing the input schema for tool definitions. This was a
mistake since
    the server is expecting a literal object for the schema.

## @gram/[email protected]

### Minor Changes

-   9fbd193: Introducing two new commands to the Gram CLI:

        gram stage openapi --slug <slug> --location <path>
        gram stage function --slug <slug> --location <path>

These commands can be used to gradually build out deployment configs by
adding OpenAPI documents and Gram Functions zip files as sources. After
    all sources are added, `gram push` can be used to deploy the staged
    configuration.

In practice, this should make it easier to script a Gram deployment in
CI/CD and
locally compared to authoring a full deployment JSON config manually.

- 30f385c: Added a `--method replace|merge` flag to the `gram push`
command. This flag
allows users to specify whether a push should replace all previous
deployment
artifacts or merge on top of them. The default behavior is `--method
merge`. As
    an illustrative example:

    **With `--method replace`:**

        T0:
          Current project artifacts:
            - petstore.openapi.yaml
            - greet.zip

        T1:
          User runs:
gram stage function --slug ecommerce --location ecommerce.zip
            gram push --method replace

        T2:
          Resulting project artifacts:
            - ecommerce (ecommerce.zip)

    **With `--method merge` (the new default behavior):**

        T0:
          Current project artifacts:
            - petstore (petstore.openapi.yaml)
            - greeter (greet.zip)

        T1:
          User runs:
gram stage function --slug ecommerce --location ecommerce.zip
            gram push --method merge

        T2:
          Resulting project artifacts:
            - petstore (petstore.openapi.yaml)
            - greeter (greet.zip)
            - ecommerce (ecommerce.zip)

### Patch Changes

- 789b304: Updated the deployment workflow in the CLI to not require a
previous deployment
    ID when evolving.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: gram-bot[bot]

.changeset/chubby-plums-itch.md

@@ -1,5 +1,72 @@
 # @gram/cli
 
+## 0.10.0
+
+### Minor Changes
+
+- 9fbd193: Introducing two new commands to the Gram CLI:
+
+  ```
+  gram stage openapi --slug <slug> --location <path>
+  gram stage function --slug <slug> --location <path>
+  ```
+
+  These commands can be used to gradually build out deployment configs by
+  adding OpenAPI documents and Gram Functions zip files as sources. After
+  all sources are added, `gram push` can be used to deploy the staged
+  configuration.
+
+  In practice, this should make it easier to script a Gram deployment in CI/CD and
+  locally compared to authoring a full deployment JSON config manually.
+
+- 30f385c: Added a `--method replace|merge` flag to the `gram push` command. This flag
+  allows users to specify whether a push should replace all previous deployment
+  artifacts or merge on top of them. The default behavior is `--method merge`. As
+  an illustrative example:
+
+  **With `--method replace`:**
+
+  ```
+  T0:
+    Current project artifacts:
+      - petstore.openapi.yaml
+      - greet.zip
+
+  T1:
+    User runs:
+      gram stage function --slug ecommerce --location ecommerce.zip
+      gram push --method replace
+
+  T2:
+    Resulting project artifacts:
+      - ecommerce (ecommerce.zip)
+  ```
+
+  **With `--method merge` (the new default behavior):**
+
+  ```
+  T0:
+    Current project artifacts:
+      - petstore (petstore.openapi.yaml)
+      - greeter (greet.zip)
+
+  T1:
+    User runs:
+      gram stage function --slug ecommerce --location ecommerce.zip
+      gram push --method merge
+
+  T2:
+    Resulting project artifacts:
+      - petstore (petstore.openapi.yaml)
+      - greeter (greet.zip)
+      - ecommerce (ecommerce.zip)
+  ```
+
+### Patch Changes
+
+- 789b304: Updated the deployment workflow in the CLI to not require a previous deployment
+  ID when evolving.
+
 ## 0.9.0
 
 ### Minor Changes

.changeset/green-worlds-find.md

@@ -1,5 +1,5 @@
 {
   "name": "@gram/cli",
-  "version": "0.9.0",
+  "version": "0.10.0",
   "private": true
 }

.changeset/lazy-birds-accept.md

@@ -1,5 +1,11 @@
 # @gram-ai/create-function
 
+## 0.2.1
+
+### Patch Changes
+
+- a8cc73e: Ensure .gitignore is scaffolded out with templating Gram Functions projects.
+
 ## 0.2.0
 
 ### Minor Changes

.changeset/neat-jars-film.md

@@ -1,7 +1,7 @@
 {
   "type": "module",
   "name": "@gram-ai/create-function",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Build AI tools and deploy them to getgram.ai",
   "keywords": [],
   "homepage": "https://github.com/speakeasy-api/gram",

.changeset/sweet-eagles-jump.md

@@ -1,5 +1,13 @@
 # @gram-ai/functions
 
+## 0.2.1
+
+### Patch Changes
+
+- 676405c: Updated the `manifest()` method of the Gram Functions TS framework to avoid
+  JSON-serializing the input schema for tool definitions. This was a mistake since
+  the server is expecting a literal object for the schema.
+
 ## 0.2.0
 
 ## 0.1.0