Skip to content

fix(release-workflow): failure caused by registry resolution during semantic-release prepare#5

Merged
lemyskaman merged 2 commits into
mainfrom
copilot/fix-github-actions-release-job
Jun 17, 2026
Merged

fix(release-workflow): failure caused by registry resolution during semantic-release prepare#5
lemyskaman merged 2 commits into
mainfrom
copilot/fix-github-actions-release-job

Conversation

Copilot AI commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

The release GitHub Actions job failed in @semantic-release/npm during npm version because npm attempted to resolve vite-plugin-flatwave-react@0.1.0 from the public registry and received a 404. This change removes that registry dependency from the workspace graph used during release preparation.

  • Release-path dependency resolution

    • Updated the example app’s dependency on the plugin from a registry version to a local workspace file reference:
      • examples/basic-react-site/package.json
        • vite-plugin-flatwave-react: "0.1.0"
        • vite-plugin-flatwave-react: "file:../../packages/vite-plugin-flatwave-react"
  • Lockfile alignment

    • Updated package-lock.json to reflect the new local file dependency so install/prepare behavior is consistent in CI.

Example of the key change:

{
  "dependencies": {
    "vite-plugin-flatwave-react": "file:../../packages/vite-plugin-flatwave-react"
  }
}

Copilot AI changed the title [WIP] Fix failing GitHub Actions job release Fix release workflow failure caused by registry resolution during semantic-release prepare Jun 17, 2026
Copilot AI requested a review from lemyskaman June 17, 2026 17:54
@lemyskaman lemyskaman changed the title Fix release workflow failure caused by registry resolution during semantic-release prepare fix(release-workflow): failure caused by registry resolution during semantic-release prepare Jun 17, 2026
@lemyskaman lemyskaman marked this pull request as ready for review June 17, 2026 17:56
@lemyskaman lemyskaman merged commit e0f62f0 into main Jun 17, 2026
3 checks 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