Paragraph Release Notes - Paragon Documentation

To update your Paragraph project to the latest version, run the following commands in your terminal:

# Update the CLI
npm install -g @useparagon/cli
# Update the core libraries in your project
para install --sync-versions

Release Notes

v1.1.1

Added slug field to Custom Integrations for consistent naming between the API and CLI. Renaming a Custom Integration’s display name no longer affects directory or import paths in Paragraph:
Custom Integration identifiers are now immutableBefore v1.1.1, changing the display name of a Custom Integration would result in a change in the integration identifier/slug (used in paragon.connect) and the integration source path (after a para pull).For example, changing “TaskLab” to “Apex Tasks” would result in a change from custom.tasklab to custom.apextasks.This identifier is now immutable and set at the time your Custom Integration is created. For existing Custom Integrations, the identifier will be set immutably to the same value it currently has in your project when you upgrade to v1.1.1.
Fixed type errors with some available Function step libraries (e.g., libphonenumber, ioredis, @aws-sdk/client-sqs).
Fixed webhook trigger step output typing so that triggerStep.output.result is no longer typed as unknown, resolving TypeScript compilation errors in synced and exported code.

v1.1.0

Added support for OAuth ROPC (Resource Owner Password Credentials) authentication and custom request options (requestOptions) in Custom Integrations.
Change in defaults for auth URL parametersBefore v1.1.0, Custom Integrations using OAuth automatically included access_type=offline as part of the query parameters for the initial authorization URL. This query parameter is no longer included by default.If you need to add this parameter (notably, Google requires this parameter for refresh tokens), define it in requestOptions.authorizationCodeOptions.configuration.queryParams.
Code Example
// In custom.[integration name]/config.ts requestOptions: { authorizationCodeOptions: { configuration: { queryParams: { access_type: 'offline', }, }, }, },
Fixed para pull to include the “Add Basic Auth header” toggle under requestOptions.accessTokenOptions for OAuth-type Custom Integrations.

v1.0.31

Added support for paragonUtils and field mapping object sources in Function steps.
Fixed an issue where referencing File variables in the “Raw” body option of a Request step could cause file data to incorrectly be stringified after pushing changes from Paragraph.
Updated Paragraph’s mysql2 and form-data dependencies for improved compatibility.

v1.0.30

Added support for workflow execution source variables (workflowExecutionId, projectId, workflowId) that can be synced between Paragon and Paragraph using para pull and para push.

v1.0.29

Adds support for “Include Client ID and Secret in Token Exchange” option for OAuth 2.0-type Resources.
Improves error messaging for deployment failures that occur during para push. Error messages will now include workflow and step names for clarity.

v1.0.28

v1.0.26

Adds support for custom cron expressions for Scheduler triggers.
Fixes an issue where using literal array values with StringIsIn operators could result in the following error:
```
You can not perform string operation on non-string data type.
```

v1.0.25

Fixes an issue where Request steps with query parameters in the URL and in the params object could cause conflicts that lead to parameters being removed after para push.

Improves variable referencing support by allowing for “bare” references.

Previously, variables would need to be interpolated as template strings:

const functionStep = new FunctionStep({
  parameters: {
    key: `${requestStep.output.body}`
  }
});

Now, they can be referenced directly:

const functionStep = new FunctionStep({
  parameters: {
    key: requestStep.output.body
  }
});

Adds a generic type parameter for FunctionStep to allow for customizable output types.

v1.0.24

Fixes Object literal may only specify known properties errors when pulling a Paragon project that uses a combination dropdown input type in the Connect Portal User Settings.
Updates compilation error messaging to reveal more detailed information instead of the following generic errors:
- persona.meta.js is not found in project
- Could not found [...]/dist/integrations/[...]/config.js.

v1.0.23

Fixes a compilation issue that could occur when using the para pull command in projects that have a Pipedrive integration.
Fixes an issue where pushing new projects initialized with Paragraph could result in a “Failed to get project comparison.” error.
Fixes an issue where Request Step Pagination used in Custom Integrations could result in a compilation error.
Adds support for referencing combination inputs, such as the Azure DevOps State input.
Adds support for using numeric values in Custom Dropdown inputs defined in Paragraph projects.

v1.0.22

Fixes an issue where nested step variables in a Request Step JSON body could create invalid references when pushing to a Paragon project.
Adds support for new Field Mapping input types, now supported for any integration. Learn more here.

v1.0.21

Fixes an issue where para pull could fail if the workflow name contains a / character.
Adds support for Password-type inputs in the Connect Portal configuration.

v1.0.20

Fixes an issue where Request steps without query parameters could cause an extra ?= to be added to the URL after pulling/pushing.

v1.0.19

Adds full support for pulling Resource Request steps.
Fixes type issues for App Event triggers using Field Mapping.
Fixes an issue where a nested object in the Request body could be pulled incorrectly as [object Object].