function-runners@0.1.0

Minor Changes

• 7cd9b62: Rename packages in changelogs, git tags and github releases

docs@0.1.0

Minor Changes

• 7cd9b62: Rename packages in changelogs, git tags and github releases

dashboard@0.16.0

Minor Changes

• 7cd9b62: Rename packages in changelogs, git tags and github releases

Patch Changes

• b6b4ed0: Better custom domain model ordering

cli@0.11.1

Patch Changes

• 54b14bb: fixed GitHub release name

cli@0.11.0

Minor Changes

• 7cd9b62: Rename packages in changelogs, git tags and github releases

@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.

@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.

@gram-ai/create-function@0.2.1

Patch Changes

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

@gram/server@0.8.1

Patch Changes

• f3cea34: The first major wave of work for supporting MCP resources through functions includes creating the function_resource_definitions data model with corresponding indexes and resource_urns columns in toolset versions. It also introduces the function manifest schema for resources and implements deployment processing for function resources. A new resource URN type is added, which parses uniqueness from the URI as the primary key for resources in MCP. Additionally, this work enables adding and returning resources throughout the toolsets data model, preserves resources within toolset versions, and updates current toolset caching to account for them.

@gram/functions@0.0.4

Patch Changes

• 468b341: Modifies the functions runner and JS entrypoint to accept handleResources entrypoint. Can differentiate between tools, resources, and potential other future entrypoints by type argument.