containers / skopeo

Work with remote images registries - retrieving information, images, signing content
Apache License 2.0
8.34k stars 786 forks source link

fix(deps): update golang.org/x/exp digest to 701f63a #2429

Closed renovate[bot] closed 1 month ago

renovate[bot] commented 1 month ago

This PR contains the following updates:

Package Type Update Change
golang.org/x/exp require digest 9b4947d -> 701f63a

Configuration

📅 Schedule: Branch creation - "after 1am and before 11am on the first day of the month" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 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.



This PR was generated by Mend Renovate. View the repository job log.

renovate[bot] commented 1 month ago

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

Details:

Package Change
golang.org/x/mod v0.20.0 -> v0.21.0
packit-as-a-service[bot] commented 1 month ago

We were not able to find or create Copr project packit/containers-skopeo-2429 specified in the config with the following error:

Cannot create a new Copr project (owner=packit project=containers-skopeo-2429 chroots=['fedora-41-x86_64', 'fedora-rawhide-aarch64', 'fedora-41-aarch64', 'fedora-rawhide-x86_64', 'fedora-40-x86_64', 'fedora-40-aarch64']): Copr: 'packit/containers-skopeo-2429' already exists. Copr HTTP response is 400 BAD REQUEST.

Unless the HTTP status code above is >= 500, please check your configuration for:

  1. typos in owner and project name (groups need to be prefixed with @)
  2. whether the project name doesn't contain not allowed characters (only letters, digits, underscores, dashes and dots must be used)
  3. whether the project itself exists (Packit creates projects only in its own namespace)
  4. whether Packit is allowed to build in your Copr project
  5. whether your Copr project/group is not private