The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Build and publish docker images

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Build and publish docker images

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Publish E2B template

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Build and upload CLI (macos-14)

Create SWE Toolkit Release (ubuntu-latest, 3.10)

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Create SWE Toolkit Release (ubuntu-latest, 3.10)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, autogen)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, camel)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, claude)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, crew_ai)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, griptape)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, julep)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, langchain)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, llamaindex)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, lyzr)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, openai)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, praisonai)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, langgraph)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, phidata)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Create Plugin Releases (ubuntu-latest, 3.10, google)

attestations input ignored

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.

Upgrade to Trusted Publishing

Create a Trusted Publisher

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Build and Release #266

Summary

Build and Release #266

Jobs

Run details

release.yaml

Annotations