Skip to content

fix: remove postinstall script from package.json to fix GitHub Action #1450

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 15, 2025

Conversation

gomessguii
Copy link
Contributor

@gomessguii gomessguii commented May 15, 2025

fix: remove postinstall script from package.json to fix GitHub Action

Summary by Sourcery

Bug Fixes:

  • Remove postinstall script invoking Prisma generate and migrate deploy

Copy link
Contributor

sourcery-ai bot commented May 15, 2025

Reviewer's Guide

Removed the automatic Prisma postinstall step from package.json and corrected script syntax to prevent GitHub Actions failures.

Sequence Diagram: Behavior of Removed postinstall Script

sequenceDiagram
    participant Installer as "Package Installer (npm/yarn)"
    participant Postinstall as "`postinstall` script (in package.json)"
    participant PrismaCLI as "Prisma CLI"

    Note over Installer, PrismaCLI: This diagram shows the interactions of the `postinstall` script that has now been removed.

    Installer->>Postinstall: (Previously) Triggered after package installation
    Postinstall->>PrismaCLI: (Previously) Executed `npx prisma generate --schema=prisma/postgresql-schema.prisma`
    Postinstall->>PrismaCLI: (Previously) Executed `npx prisma migrate deploy --schema=prisma/postgresql-schema.prisma`
Loading

File-Level Changes

Change Details Files
Remove the postinstall hook and adjust script syntax
  • Deleted the “postinstall” script entry
  • Eliminated the dangling comma after the removed entry
  • Verified the remaining script definitions maintain valid JSON
package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@DavidsonGomes DavidsonGomes merged commit b1f3c5c into EvolutionAPI:develop May 15, 2025
1 check passed
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.

2 participants