Skip to content

Conversation

@ShadowCat567
Copy link
Contributor

When attempting to publish packages from amplify backend using trusted publishing, this error was appearing:

 error an error occurred while publishing @aws-amplify/backend-*: E422 422 Unprocessable Entity - PUT https://registry.npmjs.org/@aws-amplify%2fbackend-* - Error verifying sigstore provenance bundle: Failed to validate repository information: package.json: "repository.url" is "", expected to match "https://github.com/aws-amplify/amplify-backend" from provenance

Updated the packge.json files in all of our public packages to include:

"repository": {
    "type": "git",
    "url": "https://github.com/aws-amplify/amplify-backend.git"
  },

to fix this error.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@changeset-bot
Copy link

changeset-bot bot commented Oct 24, 2025

🦋 Changeset detected

Latest commit: 1b4ccc9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 24 packages
Name Type
@aws-amplify/deployed-backend-client Patch
@aws-amplify/backend-output-schemas Patch
@aws-amplify/backend-output-storage Patch
@aws-amplify/backend-deployer Patch
@aws-amplify/backend-function Patch
@aws-amplify/schema-generator Patch
@aws-amplify/backend-storage Patch
@aws-amplify/model-generator Patch
@aws-amplify/auth-construct Patch
@aws-amplify/backend-secret Patch
create-amplify Patch
@aws-amplify/form-generator Patch
@aws-amplify/ai-constructs Patch
@aws-amplify/client-config Patch
@aws-amplify/platform-core Patch
@aws-amplify/backend-auth Patch
@aws-amplify/backend-data Patch
@aws-amplify/plugin-types Patch
@aws-amplify/backend-ai Patch
@aws-amplify/cli-core Patch
@aws-amplify/backend Patch
@aws-amplify/sandbox Patch
ampx Patch
@aws-amplify/seed Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant