feeldata/feeldata.app
Watch
5
0
Fork
You've already forked feeldata.app
 0
Code Issues 22 Pull requests 1 Projects Releases Packages Activity

fix(deps): update dependency @vercel/otel to v2 #262

Closed
b4mad-renovate wants to merge 1 commit from renovate/vercel-otel-2.x into main
pull from: renovate/vercel-otel-2.x
merge into: feeldata:main
Conversation 20 Commits 1 Files changed 1 +1 -1
b4mad-renovate commented 2025-09-29 12:06:56 +00:00 (Migrated from codeberg.org)
Copy link

This PR contains the following updates:

Package Change Age Confidence
@vercel/otel ^1.8.1 → ^1.8.1 || ^2.0.0 age confidence

Release Notes

vercel/otel (@​vercel/otel)

v2.1.2

Compare Source

Patch Changes

v2.1.1

Compare Source

Patch Changes

v2.1.0

Compare Source

Minor Changes
  • #​181 14f773c Thanks @​dvoytenko! - Ignore auto-configuration based on the OTEL_EXPORTER_OTLP_ env vars when trace drains are used. This avoids duplicate trace export.

v2.0.1

Compare Source

Patch Changes

v2.0.0

Compare Source

Major Changes

Breaking Changes

1. OpenTelemetry SDK dependencies updated
**API package** (minimum version bumped):

-   `@opentelemetry/api`: `>=1.9.0 <3.0.0` (was `>=1.7.0 <2.0.0`)

**Stable packages** (updated to v2.x):

-   `@opentelemetry/resources`: `>=2.0.0 <3.0.0` (was `>=1.19.0 <2.0.0`)
-   `@opentelemetry/sdk-metrics`: `>=2.0.0 <3.0.0` (was `>=1.19.0 <2.0.0`)
-   `@opentelemetry/sdk-trace-base`: `>=2.0.0 <3.0.0` (was `>=1.19.0 <2.0.0`)

**Experimental packages** (updated to v0.2XX):

-   `@opentelemetry/api-logs`: `>=0.200.0 <0.300.0` (was `>=0.46.0 <0.200.0`)
-   `@opentelemetry/instrumentation`: `>=0.200.0 <0.300.0` (was `>=0.46.0 <0.200.0`)
-   `@opentelemetry/sdk-logs`: `>=0.200.0 <0.300.0` (was `>=0.46.0 <0.200.0`)
2. Minimum Node.js version requirement
The minimum supported Node.js has been raised to `^18.19.0 || >=20.6.0` to align with OpenTelemetry JS SDK 2.x requirements. This means that support for Node.js 14 and 16 has been dropped.
3. Configuration changes
**Log Record Processors:**

```typescript
// Before (v1.x)
registerOTel({
  serviceName: "your-service-name",
  logRecordProcessor: myProcessor, // Single processor
});

// After (v2.x)
registerOTel({
  serviceName: "your-service-name",
  logRecordProcessors: [myProcessor], // Array of processors
});
```

**Metric Readers:**

```typescript
// Before (v1.x)
registerOTel({
  serviceName: "your-service-name",
  metricReader: myReader, // Single reader
});

// After (v2.x)
registerOTel({
  serviceName: "your-service-name",
  metricReaders: [myReader], // Array of readers
});
```

Migration Guide

1.  **Update OpenTelemetry dependencies**: Update the OpenTelemetry packages you are using in your project to the compatible versions:

    **API package** (minimum version bumped):

    ```bash
    npm install @&#8203;opentelemetry/api@^1.9.0
    ```

    **Stable packages** (upgrade to v2.x):

    ```bash
    npm install @&#8203;opentelemetry/resources@^2.1.0 @&#8203;opentelemetry/sdk-trace-base@^2.1.0 @&#8203;opentelemetry/sdk-metrics@^2.1.0
    ```

    **Experimental packages** (upgrade to v0.2XX):

    ```bash
    npm install @&#8203;opentelemetry/sdk-logs@^0.205.0 @&#8203;opentelemetry/instrumentation@^0.205.0 @&#8203;opentelemetry/api-logs@^0.205.0
    ```

    **Note**: Only install the packages you are actually using in your project.

2.  **Update configuration**:

    **Log Record Processors** - Change `logRecordProcessor` to `logRecordProcessors`:

    ```typescript
    // Before
    registerOTel({
      serviceName: 'your-service-name',
      logRecordProcessor: myProcessor // Single processor
    });

    // After
    registerOTel({
      serviceName: 'your-service-name',
      logRecordProcessors: [myProcessor], // Array of processors
    });
    ```

    **Metric Readers** - Change `metricReader` to `metricReaders`:

    ```typescript
    // Before
    registerOTel({
      serviceName: 'your-service-name',
      metricReader: myReader, // Single processor
    });

    // After
    registerOtel({
      serviceName: 'your-service-name',
      metricReaders: [myReader], // Array of processors
    });
    ```

3.  **No code changes needed** for basic usage - the SDK interface remains the same for most common use cases.

For complete details on migrating from OpenTelemetry JS SDK 1.x to 2.x, see the [official OpenTelemetry migration guide](https://github.com/open-telemetry/opentelemetry-js/blob/v2.0.0/doc/upgrade-to-2.x.md).

v1.14.1

Compare Source

Patch Changes

v1.14.0

Compare Source

Minor Changes
  • #​182 e44a0d8 Thanks @​dvoytenko! - Ignore auto-configuration based on the OTEL_EXPORTER_OTLP_ env vars when trace drains are used. This avoids duplicate trace export.

v1.13.1

Compare Source

Patch Changes

v1.13.0

Compare Source

Minor Changes
  • a724e57: add support for auto HTTP instrumentation
  • d04fbdd: Expand a set of OTEL versions for peer dependencies

v1.12.0

Compare Source

Minor Changes
  • 26167e7: Fixes an issue where VERCEL_OTEL_ENDPOINTS is not set

v1.11.0

Compare Source

Minor Changes
  • bc25833: Releases the vercel-runtime trace propagator and span processor

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • Every minute (* * * * *)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@vercel/otel](https://github.com/vercel/otel) | [`^1.8.1` → `^1.8.1 \|\| ^2.0.0`](https://renovatebot.com/diffs/npm/@vercel%2fotel/1.10.4/2.1.2) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@vercel%2fotel/2.1.2?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@vercel%2fotel/1.10.4/2.1.2?slim=true) | --- ### Release Notes <details> <summary>vercel/otel (@&#8203;vercel/otel)</summary> ### [`v2.1.2`](https://github.com/vercel/otel/releases/tag/%40vercel/otel%402.1.2) [Compare Source](https://github.com/vercel/otel/compare/@vercel/otel@2.1.1...@vercel/otel@2.1.2) ##### Patch Changes - [#&#8203;193](https://github.com/vercel/otel/pull/193) [`937e29a`](https://github.com/vercel/otel/commit/937e29aa4ee0bbdbc446162cee64cef902cff74b) Thanks [@&#8203;kakadiadarpan](https://github.com/kakadiadarpan)! - Add standard OpenTelemetry resource attributes for VCS. ### [`v2.1.1`](https://github.com/vercel/otel/releases/tag/%40vercel/otel%402.1.1) [Compare Source](https://github.com/vercel/otel/compare/@vercel/otel@2.1.0...@vercel/otel@2.1.1) ##### Patch Changes - [#&#8203;190](https://github.com/vercel/otel/pull/190) [`41d4511`](https://github.com/vercel/otel/commit/41d45110fa6e040941a7a783cf3163e2cd75a372) Thanks [@&#8203;mischnic](https://github.com/mischnic)! - fix: don't inline system env vars ### [`v2.1.0`](https://github.com/vercel/otel/releases/tag/%40vercel/otel%402.1.0) [Compare Source](https://github.com/vercel/otel/compare/@vercel/otel@2.0.1...@vercel/otel@2.1.0) ##### Minor Changes - [#&#8203;181](https://github.com/vercel/otel/pull/181) [`14f773c`](https://github.com/vercel/otel/commit/14f773c2666fcfe418e9a1a0d4205d08c8f23fd1) Thanks [@&#8203;dvoytenko](https://github.com/dvoytenko)! - Ignore auto-configuration based on the OTEL\_EXPORTER\_OTLP\_ env vars when trace drains are used. This avoids duplicate trace export. ### [`v2.0.1`](https://github.com/vercel/otel/releases/tag/%40vercel/otel%402.0.1) [Compare Source](https://github.com/vercel/otel/compare/@vercel/otel@2.0.0...@vercel/otel@2.0.1) ##### Patch Changes - [#&#8203;170](https://github.com/vercel/otel/pull/170) [`9a695ad`](https://github.com/vercel/otel/commit/9a695ad2edb76c43de8faa4d1e03c0944e21e6f8) Thanks [@&#8203;kakadiadarpan](https://github.com/kakadiadarpan)! - add project id to resource attributes ### [`v2.0.0`](https://github.com/vercel/otel/releases/tag/%40vercel/otel%402.0.0) [Compare Source](https://github.com/vercel/otel/compare/@vercel/otel@1.14.1...@vercel/otel@2.0.0) ##### Major Changes - [#&#8203;165](https://github.com/vercel/otel/pull/165) [`7887411`](https://github.com/vercel/otel/commit/788741179c9a96269d59a12acb3d10fc70ff8262) Thanks [@&#8203;bengigone](https://github.com/bengigone)! - Add support for OTel JS SDK 2.X #### Breaking Changes ##### 1. OpenTelemetry SDK dependencies updated ``` **API package** (minimum version bumped): - `@opentelemetry/api`: `>=1.9.0 <3.0.0` (was `>=1.7.0 <2.0.0`) **Stable packages** (updated to v2.x): - `@opentelemetry/resources`: `>=2.0.0 <3.0.0` (was `>=1.19.0 <2.0.0`) - `@opentelemetry/sdk-metrics`: `>=2.0.0 <3.0.0` (was `>=1.19.0 <2.0.0`) - `@opentelemetry/sdk-trace-base`: `>=2.0.0 <3.0.0` (was `>=1.19.0 <2.0.0`) **Experimental packages** (updated to v0.2XX): - `@opentelemetry/api-logs`: `>=0.200.0 <0.300.0` (was `>=0.46.0 <0.200.0`) - `@opentelemetry/instrumentation`: `>=0.200.0 <0.300.0` (was `>=0.46.0 <0.200.0`) - `@opentelemetry/sdk-logs`: `>=0.200.0 <0.300.0` (was `>=0.46.0 <0.200.0`) ``` ##### 2. Minimum Node.js version requirement ``` The minimum supported Node.js has been raised to `^18.19.0 || >=20.6.0` to align with OpenTelemetry JS SDK 2.x requirements. This means that support for Node.js 14 and 16 has been dropped. ``` ##### 3. Configuration changes ```` **Log Record Processors:** ```typescript // Before (v1.x) registerOTel({ serviceName: "your-service-name", logRecordProcessor: myProcessor, // Single processor }); // After (v2.x) registerOTel({ serviceName: "your-service-name", logRecordProcessors: [myProcessor], // Array of processors }); ``` **Metric Readers:** ```typescript // Before (v1.x) registerOTel({ serviceName: "your-service-name", metricReader: myReader, // Single reader }); // After (v2.x) registerOTel({ serviceName: "your-service-name", metricReaders: [myReader], // Array of readers }); ``` ```` #### Migration Guide ```` 1. **Update OpenTelemetry dependencies**: Update the OpenTelemetry packages you are using in your project to the compatible versions: **API package** (minimum version bumped): ```bash npm install @&#8203;opentelemetry/api@^1.9.0 ``` **Stable packages** (upgrade to v2.x): ```bash npm install @&#8203;opentelemetry/resources@^2.1.0 @&#8203;opentelemetry/sdk-trace-base@^2.1.0 @&#8203;opentelemetry/sdk-metrics@^2.1.0 ``` **Experimental packages** (upgrade to v0.2XX): ```bash npm install @&#8203;opentelemetry/sdk-logs@^0.205.0 @&#8203;opentelemetry/instrumentation@^0.205.0 @&#8203;opentelemetry/api-logs@^0.205.0 ``` **Note**: Only install the packages you are actually using in your project. 2. **Update configuration**: **Log Record Processors** - Change `logRecordProcessor` to `logRecordProcessors`: ```typescript // Before registerOTel({ serviceName: 'your-service-name', logRecordProcessor: myProcessor // Single processor }); // After registerOTel({ serviceName: 'your-service-name', logRecordProcessors: [myProcessor], // Array of processors }); ``` **Metric Readers** - Change `metricReader` to `metricReaders`: ```typescript // Before registerOTel({ serviceName: 'your-service-name', metricReader: myReader, // Single processor }); // After registerOtel({ serviceName: 'your-service-name', metricReaders: [myReader], // Array of processors }); ``` 3. **No code changes needed** for basic usage - the SDK interface remains the same for most common use cases. For complete details on migrating from OpenTelemetry JS SDK 1.x to 2.x, see the [official OpenTelemetry migration guide](https://github.com/open-telemetry/opentelemetry-js/blob/v2.0.0/doc/upgrade-to-2.x.md). ```` ### [`v1.14.1`](https://github.com/vercel/otel/releases/tag/%40vercel/otel%401.14.1) [Compare Source](https://github.com/vercel/otel/compare/@vercel/otel@1.14.0...@vercel/otel@1.14.1) ##### Patch Changes - [#&#8203;194](https://github.com/vercel/otel/pull/194) [`5eef3a6`](https://github.com/vercel/otel/commit/5eef3a6efab9131ca8faccf114e3e10063e8bf61) Thanks [@&#8203;kakadiadarpan](https://github.com/kakadiadarpan)! - Add standard OpenTelemetry resource attributes for VCS. ### [`v1.14.0`](https://github.com/vercel/otel/releases/tag/%40vercel/otel%401.14.0) [Compare Source](https://github.com/vercel/otel/compare/@vercel/otel@1.13.1...@vercel/otel@1.14.0) ##### Minor Changes - [#&#8203;182](https://github.com/vercel/otel/pull/182) [`e44a0d8`](https://github.com/vercel/otel/commit/e44a0d8dbc10d1b58b02ab272543a7574b4147e9) Thanks [@&#8203;dvoytenko](https://github.com/dvoytenko)! - Ignore auto-configuration based on the OTEL\_EXPORTER\_OTLP\_ env vars when trace drains are used. This avoids duplicate trace export. ### [`v1.13.1`](https://github.com/vercel/otel/releases/tag/%40vercel/otel%401.13.1) [Compare Source](https://github.com/vercel/otel/compare/@vercel/otel@1.13.0...@vercel/otel@1.13.1) ##### Patch Changes - [#&#8203;171](https://github.com/vercel/otel/pull/171) [`2b353dd`](https://github.com/vercel/otel/commit/2b353dd798c8e8d8aef4a33da75e3b50ffb13d05) Thanks [@&#8203;kakadiadarpan](https://github.com/kakadiadarpan)! - add project id to resource attributes ### [`v1.13.0`](https://github.com/vercel/otel/releases/tag/%40vercel/otel%401.13.0) [Compare Source](https://github.com/vercel/otel/compare/@vercel/otel@1.12.0...@vercel/otel@1.13.0) ##### Minor Changes - [`a724e57`](https://github.com/vercel/otel/commit/a724e57): add support for auto HTTP instrumentation - [`d04fbdd`](https://github.com/vercel/otel/commit/d04fbdd): Expand a set of OTEL versions for peer dependencies ### [`v1.12.0`](https://github.com/vercel/otel/releases/tag/%40vercel/otel%401.12.0) [Compare Source](https://github.com/vercel/otel/compare/@vercel/otel@1.11.0...@vercel/otel@1.12.0) ##### Minor Changes - [`26167e7`](https://github.com/vercel/otel/commit/26167e7): Fixes an issue where VERCEL\_OTEL\_ENDPOINTS is not set ### [`v1.11.0`](https://github.com/vercel/otel/releases/tag/%40vercel/otel%401.11.0) [Compare Source](https://github.com/vercel/otel/compare/@vercel/otel@1.10.4...@vercel/otel@1.11.0) ##### Minor Changes - [`bc25833`](https://github.com/vercel/otel/commit/bc25833): Releases the `vercel-runtime` trace propagator and span processor </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - Every minute (`* * * * *`) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xMjIuMyIsInVwZGF0ZWRJblZlciI6IjQzLjE2OC42IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
b4mad-renovate commented 2025-09-29 12:06:58 +00:00 (Migrated from codeberg.org)
Copy link

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: feeldata.app@0.10.2
npm error Found: @storybook/addon-a11y@9.2.0-alpha.1
npm error node_modules/@storybook/addon-a11y
npm error   dev @storybook/addon-a11y@"^10.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error dev @storybook/addon-a11y@"^10.0.0" from the root project
npm error
npm error Conflicting peer dependency: storybook@10.3.6
npm error node_modules/storybook
npm error   peer storybook@"^10.3.6" from @storybook/addon-a11y@10.3.6
npm error   node_modules/@storybook/addon-a11y
npm error     dev @storybook/addon-a11y@"^10.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-05-12T08_15_21_657Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-05-12T08_15_21_657Z-debug-0.log
### ⚠️ Artifact update problem Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: package-lock.json ``` npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: feeldata.app@0.10.2 npm error Found: @storybook/addon-a11y@9.2.0-alpha.1 npm error node_modules/@storybook/addon-a11y npm error dev @storybook/addon-a11y@"^10.0.0" from the root project npm error npm error Could not resolve dependency: npm error dev @storybook/addon-a11y@"^10.0.0" from the root project npm error npm error Conflicting peer dependency: storybook@10.3.6 npm error node_modules/storybook npm error peer storybook@"^10.3.6" from @storybook/addon-a11y@10.3.6 npm error node_modules/@storybook/addon-a11y npm error dev @storybook/addon-a11y@"^10.0.0" from the root project npm error npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error /tmp/renovate/cache/others/npm/_logs/2026-05-12T08_15_21_657Z-eresolve-report.txt npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-05-12T08_15_21_657Z-debug-0.log ```
op1st-gitops commented 2025-09-29 12:06:59 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-z4hbw is running.

Starting Pipelinerun on-pull-request-z4hbw in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-z4hbw -f

op1st Pipelines as Code/on-pull-request-z4hbw is running. Starting Pipelinerun <b>on-pull-request-z4hbw</b> in namespace<b> feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-z4hbw) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-z4hbw -f</code>
op1st-gitops commented 2025-09-29 12:09:07 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-z4hbw has successfully validated your commit.

Task Statuses:

StatusDurationName
Succeeded 15 seconds

fetch-source-repository

Succeeded 1 minute

unit-tests

op1st Pipelines as Code/on-pull-request-z4hbw has <b>successfully</b> validated your commit. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">feeldata-dev</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-z4hbw">on-pull-request-z4hbw</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>15 seconds</td><td> [fetch-source-repository](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-z4hbw/logs/fetch-source-repository) </td></tr> <tr> <td>Succeeded</td> <td>1 minute</td><td> [unit-tests](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-z4hbw/logs/unit-tests) </td></tr> </table>
op1st-gitops commented 2025-10-01 04:08:04 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-8n58k is running.

Starting Pipelinerun on-pull-request-8n58k in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-8n58k -f

op1st Pipelines as Code/on-pull-request-8n58k is running. Starting Pipelinerun <b>on-pull-request-8n58k</b> in namespace<b> feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-8n58k) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-8n58k -f</code>
op1st-gitops commented 2025-10-01 04:14:00 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-8n58k has successfully validated your commit.

Task Statuses:

StatusDurationName
Succeeded 3 minutes

fetch-source-repository

Succeeded 2 minutes

unit-tests

op1st Pipelines as Code/on-pull-request-8n58k has <b>successfully</b> validated your commit. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">feeldata-dev</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-8n58k">on-pull-request-8n58k</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>3 minutes</td><td> [fetch-source-repository](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-8n58k/logs/fetch-source-repository) </td></tr> <tr> <td>Succeeded</td> <td>2 minutes</td><td> [unit-tests](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-8n58k/logs/unit-tests) </td></tr> </table>
op1st-gitops commented 2025-10-08 04:06:30 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-hhfl2 is running.

Starting Pipelinerun on-pull-request-hhfl2 in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-hhfl2 -f

op1st Pipelines as Code/on-pull-request-hhfl2 is running. Starting Pipelinerun <b>on-pull-request-hhfl2</b> in namespace<b> feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-hhfl2) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-hhfl2 -f</code>
op1st-gitops commented 2025-10-08 04:08:34 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-hhfl2 has successfully validated your commit.

Task Statuses:

StatusDurationName
Succeeded 9 seconds

fetch-source-repository

Succeeded 1 minute

unit-tests

op1st Pipelines as Code/on-pull-request-hhfl2 has <b>successfully</b> validated your commit. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">feeldata-dev</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-hhfl2">on-pull-request-hhfl2</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>9 seconds</td><td> [fetch-source-repository](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-hhfl2/logs/fetch-source-repository) </td></tr> <tr> <td>Succeeded</td> <td>1 minute</td><td> [unit-tests](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-hhfl2/logs/unit-tests) </td></tr> </table>
op1st-gitops commented 2025-10-09 11:07:34 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-6wn8h is running.

Starting Pipelinerun on-pull-request-6wn8h in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-6wn8h -f

op1st Pipelines as Code/on-pull-request-6wn8h is running. Starting Pipelinerun <b>on-pull-request-6wn8h</b> in namespace<b> feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-6wn8h) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-6wn8h -f</code>
op1st-gitops commented 2025-10-09 11:12:09 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-6wn8h has successfully validated your commit.

Task Statuses:

StatusDurationName
Succeeded 18 seconds

fetch-source-repository

Succeeded 4 minutes

unit-tests

op1st Pipelines as Code/on-pull-request-6wn8h has <b>successfully</b> validated your commit. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">feeldata-dev</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-6wn8h">on-pull-request-6wn8h</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>18 seconds</td><td> [fetch-source-repository](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-6wn8h/logs/fetch-source-repository) </td></tr> <tr> <td>Succeeded</td> <td>4 minutes</td><td> [unit-tests](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-6wn8h/logs/unit-tests) </td></tr> </table>
op1st-gitops commented 2025-10-13 14:07:41 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-knhdp is running.

Starting Pipelinerun on-pull-request-knhdp in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-knhdp -f

op1st Pipelines as Code/on-pull-request-knhdp is running. Starting Pipelinerun <b>on-pull-request-knhdp</b> in namespace<b> feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-knhdp) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-knhdp -f</code>
op1st-gitops commented 2025-10-13 14:25:37 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-knhdp has successfully validated your commit.

Task Statuses:

StatusDurationName
Succeeded 31 seconds

fetch-source-repository

Succeeded 17 minutes

unit-tests

op1st Pipelines as Code/on-pull-request-knhdp has <b>successfully</b> validated your commit. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">feeldata-dev</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-knhdp">on-pull-request-knhdp</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>31 seconds</td><td> [fetch-source-repository](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-knhdp/logs/fetch-source-repository) </td></tr> <tr> <td>Succeeded</td> <td>17 minutes</td><td> [unit-tests](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-knhdp/logs/unit-tests) </td></tr> </table>
op1st-gitops commented 2025-10-14 18:07:06 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-87l8v is running.

Starting Pipelinerun on-pull-request-87l8v in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-87l8v -f

op1st Pipelines as Code/on-pull-request-87l8v is running. Starting Pipelinerun <b>on-pull-request-87l8v</b> in namespace<b> feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-87l8v) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-87l8v -f</code>
op1st-gitops commented 2025-10-15 04:07:04 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-nvtvt is running.

Starting Pipelinerun on-pull-request-nvtvt in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-nvtvt -f

op1st Pipelines as Code/on-pull-request-nvtvt is running. Starting Pipelinerun <b>on-pull-request-nvtvt</b> in namespace<b> feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-nvtvt) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-nvtvt -f</code>
op1st-gitops commented 2025-10-22 02:53:37 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-nr22v is running.

Starting Pipelinerun on-pull-request-nr22v in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-nr22v -f

op1st Pipelines as Code/on-pull-request-nr22v is running. Starting Pipelinerun <b>on-pull-request-nr22v</b> in namespace<b> feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-nr22v) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-nr22v -f</code>
op1st-gitops commented 2025-11-21 06:57:02 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code has failed.
There was an error creating the PipelineRun: on-pull-request-

cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 7 comments in 5 minutes: rate limited

op1st Pipelines as Code has <b>failed</b>. There was an error creating the PipelineRun: <b>on-pull-request-</b> cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 7 comments in 5 minutes: rate limited
op1st-gitops commented 2025-11-21 07:23:13 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code has failed.
There was an error creating the PipelineRun: on-pull-request-

cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 6 comments in 5 minutes: rate limited

op1st Pipelines as Code has <b>failed</b>. There was an error creating the PipelineRun: <b>on-pull-request-</b> cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 6 comments in 5 minutes: rate limited
op1st-gitops commented 2025-11-21 07:38:24 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code has failed.
There was an error creating the PipelineRun: on-pull-request-

cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 16 comments in 30 minutes: rate limited

op1st Pipelines as Code has <b>failed</b>. There was an error creating the PipelineRun: <b>on-pull-request-</b> cannot use the API on the provider platform to create a in_progress status: CreateComment: "op1st-gitops" posted 16 comments in 30 minutes: rate limited
op1st-gitops commented 2025-11-28 07:07:08 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-9crcq is running.

Starting Pipelinerun on-pull-request-9crcq in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-9crcq -f

op1st Pipelines as Code/on-pull-request-9crcq is running. Starting Pipelinerun <b>[on-pull-request-9crcq](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-9crcq)</b> in namespace <b>feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-9crcq) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-9crcq -f</code>
op1st-gitops commented 2025-12-13 18:05:14 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-fzxkd is running.

Starting Pipelinerun on-pull-request-fzxkd in namespace feeldata-dev

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n feeldata-dev on-pull-request-fzxkd -f

op1st Pipelines as Code/on-pull-request-fzxkd is running. Starting Pipelinerun <b>[on-pull-request-fzxkd](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-fzxkd)</b> in namespace <b>feeldata-dev</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-fzxkd) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n feeldata-dev on-pull-request-fzxkd -f</code>
op1st-gitops commented 2025-12-13 18:06:02 +00:00 (Migrated from codeberg.org)
Copy link

op1st Pipelines as Code/on-pull-request-fzxkd has failed.

Task Statuses:

StatusDurationName
Succeeded 11 seconds

fetch-source-repository

Failed 29 seconds

unit-tests

Failure snippet:

task unit-tests has the status "Failed": 
> jest -c jest.config.d/units.ts --randomize --rootDir=. --coverage --verbose

sh: line 1: jest: command not found

op1st Pipelines as Code/on-pull-request-fzxkd has <b>failed</b>. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">feeldata-dev</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-fzxkd">on-pull-request-fzxkd</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>11 seconds</td><td> [fetch-source-repository](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-fzxkd/logs/fetch-source-repository) </td></tr> <tr> <td>Failed</td> <td>29 seconds</td><td> [unit-tests](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/feeldata-dev/tekton.dev~v1beta1~PipelineRun/on-pull-request-fzxkd/logs/unit-tests) </td></tr> </table> <hr> <h4>Failure snippet:</h4> task <b>unit-tests</b> has the status <b>"Failed"</b>: <pre>> jest -c jest.config.d/units.ts --randomize --rootDir=. --coverage --verbose sh: line 1: jest: command not found</pre>

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
Kind/Breaking
Breaking change that won't be backward compatible

  
Kind/Bug
Something is not working

  
Kind/Documentation
Documentation changes

  
Kind/Enhancement
Improve existing functionality

  
Kind/Feature
New functionality

  
Kind/Security
This is security issue

  
Kind/Testing
Issue or pull request related to testing

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Reviewed
Confirmed
 Issue has been confirmed

  
Reviewed
Duplicate
 This issue or pull request already exists

  
Reviewed
Invalid
 Invalid issue

  
Reviewed
Won't Fix
 This issue won't be fixed

  
Status
Abandoned
 Somebody has started to work on this but abandoned work

  
Status
Blocked
 Something is blocking this issue or pull request

  
Status
Need More Info
 Feedback is required to reproduce issue or to continue work

No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
feeldata/feeldata.app!262
No description provided.