ReleasePipeline
All release pipelines in the workspace, with optional filtering and sorting.
Table-Specific Information
SELECT
The driver uses the Linear API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client-side within the driver.| Column | Supported Operators |
| id | =, !=, IN, NOT IN |
| createdAt | =, !=, IN, NOT IN, <, <=, >, >= |
| updatedAt | =, !=, IN, NOT IN, <, <=, >, >= |
| name | =, !=, IN, NOT IN, LIKE, CONTAINS |
| type | =, !=, IN, NOT IN, IS, IS NOT |
| isProduction | =, != |
For example, the following queries are processed server-side:
SELECT * FROM ReleasePipeline LIMIT 1
SELECT * FROM ReleasePipeline WHERE isProduction = true LIMIT 1
INSERT
To insert a ReleasePipeline record:INSERT INTO ReleasePipeline (name, slugId, type, isProduction, autoGenerateReleaseNotesOnCompletion, rolloverIssuesOnCompletion) VALUES ('Main Pipeline', 'main-pipeline', 'standard', true, true, false)
UPDATE
To update a ReleasePipeline record:UPDATE ReleasePipeline SET name = 'Production Pipeline' WHERE id = '921cb6bf-d5b6-44bb-9c6b-217b97dd27a2'
DELETE
To delete a ReleasePipeline record:DELETE FROM ReleasePipeline WHERE id = '921cb6bf-d5b6-44bb-9c6b-217b97dd27a2'
Columns
| Name | Type | ReadOnly | Description |
| id [KEY] | String | False |
The unique identifier of the entity. |
| createdAt | Datetime | True |
The time at which the entity was created. |
| updatedAt | Datetime | True |
The last time at which the entity was meaningfully updated. This is the same as the creation time if the entity hasn't been updated after creation. |
| archivedAt | Datetime | True |
The time at which the entity was archived. Null if the entity has not been archived. |
| name | String | False |
The name of the pipeline. |
| slugId | String | False |
The pipeline's unique slug identifier, used in URLs and for lookup by human-readable identifier instead of UUID. |
| type | String | False |
The type of the pipeline, which determines how releases are created and managed. Continuous pipelines create a completed release per sync, while scheduled pipelines accumulate issues in a started release. |
| isProduction | Bool | False |
Whether this pipeline targets a production environment. Defaults to true. Used to distinguish production pipelines from staging or development pipelines. |
| autoGenerateReleaseNotesOnCompletion | Bool | False |
Whether to automatically generate a release note when a release is completed. |
| rolloverIssuesOnCompletion | Bool | False |
Whether completing a scheduled release moves its open issues to the next release. When false, open issues remain on the completed release. |
| includePathPatterns | String | False |
Glob patterns to filter commits by file path. When non-empty, only commits that modify files matching at least one pattern will be included in release syncs. An empty array means all commits are included regardless of file paths. Returned as a JSON array of String values; accepts a JSON array or a comma-separated list when written. |
| approximateReleaseCount | Int | True |
The approximate number of non-archived releases in this pipeline. This is a denormalized count that is updated when releases are created or archived, and may not reflect the exact count at all times. |
| trashed | Bool | True |
A flag that indicates whether the pipeline is in the trash bin. Trashed pipelines are archived and will be permanently deleted after a retention period. Null when the pipeline is not trashed. |
| latestReleaseNoteId | String | True |
The release note in this pipeline whose covered range ends with the most recent release. |
| url | String | True |
The URL to the release pipeline's releases list in the Linear app. |