Skip to content
Back to pull request #1399

PORTALS-3308 - What's in Portals Component (GoalsV2) #3722

Sign in to view logs

PORTALS-3308 - What's in Portals Component (GoalsV2)

PORTALS-3308 - What's in Portals Component (GoalsV2) #3722

Triggered via pull request December 6, 2024 17:48
@afwilliaafwillia
synchronize #1399
afwillia:PORTALS-3308
Status Success
Total duration 2m 27s
Artifacts –

npmpublish.yml

on: pull_request
Matrix: tag-and-publish
Fit to window
Zoom out
Zoom in

Annotations

22 warnings
tag-and-publish (@sage-bionetworks/markdown-it-container)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
tag-and-publish (@sage-bionetworks/markdown-it-container): packages/markdown-it-container/index.mjs#L7
Unsafe call of a(n) `any` typed value
tag-and-publish (@sage-bionetworks/markdown-it-container): packages/markdown-it-container/index.mjs#L7
Unsafe call of a(n) `any` typed value
tag-and-publish (@sage-bionetworks/markdown-it-container): packages/markdown-it-container/index.mjs#L7
Unsafe member access .trim on an `any` value
tag-and-publish (@sage-bionetworks/markdown-it-container): packages/markdown-it-container/index.mjs#L7
Unsafe member access .split on an `any` value
tag-and-publish (@sage-bionetworks/markdown-it-container): packages/markdown-it-container/index.mjs#L7
Unsafe member access [0] on an `any` value
tag-and-publish (@sage-bionetworks/markdown-it-container): packages/markdown-it-container/index.mjs#L12
Unsafe member access [idx] on an `any` value
tag-and-publish (@sage-bionetworks/markdown-it-container): packages/markdown-it-container/index.mjs#L12
Computed name [idx] resolves to an `any` value
tag-and-publish (@sage-bionetworks/markdown-it-container): packages/markdown-it-container/index.mjs#L13
Unsafe call of a(n) `any` typed value
tag-and-publish (@sage-bionetworks/markdown-it-container): packages/markdown-it-container/index.mjs#L13
Unsafe member access [idx] on an `any` value
tag-and-publish (@sage-bionetworks/markdown-it-container): packages/markdown-it-container/index.mjs#L13
Computed name [idx] resolves to an `any` value
tag-and-publish (@sage-bionetworks/markdown-it-container)
This workflow run topped the commit limit set by GitHub webhooks: that means that commits could not appear and that the run could not find the version change.
tag-and-publish (@sage-bionetworks/synapse-types)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
tag-and-publish (@sage-bionetworks/synapse-types)
This workflow run topped the commit limit set by GitHub webhooks: that means that commits could not appear and that the run could not find the version change.
tag-and-publish (markdown-it-synapse)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
tag-and-publish (markdown-it-synapse)
This workflow run topped the commit limit set by GitHub webhooks: that means that commits could not appear and that the run could not find the version change.
tag-and-publish (markdown-it-synapse-table)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
tag-and-publish (markdown-it-synapse-table)
This workflow run topped the commit limit set by GitHub webhooks: that means that commits could not appear and that the run could not find the version change.
tag-and-publish (@sage-bionetworks/synapse-client)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
tag-and-publish (@sage-bionetworks/synapse-client)
This workflow run topped the commit limit set by GitHub webhooks: that means that commits could not appear and that the run could not find the version change.
tag-and-publish (synapse-react-client)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
tag-and-publish (synapse-react-client)
This workflow run topped the commit limit set by GitHub webhooks: that means that commits could not appear and that the run could not find the version change.