bitovi / github-actions-storybook-to-github-pages

Deploy a Storybook build to GitHub Pages
MIT License
34 stars 5 forks source link

No uploaded artifact was found! #6

Closed adriansmierciaktsh closed 10 months ago

adriansmierciaktsh commented 10 months ago

Artifact exchange URL: https://pipelinesghubeus9.actions.githubusercontent.com/U75tv9vGjEbD6ncDaJJHwN3tmcm6NWn3Y6dcQr2iyjh0T4I1lG/_apis/pipelines/workflows/7221683194/artifacts?api-version=6.0-preview

Error: Error: No uploaded artifact was found! Please check if there are any errors at build step, or uploaded artifact name is correct. at getSignedArtifactUrl (/home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/src/api-client.js:93:1) at processTicksAndRejections (node:internal/process/task_queues:96:5) at Deployment.create (/home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/src/deployment.js:53:1) at main (/home/runner/work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/src/index.js:30:1)

pkmelee337 commented 10 months ago

Yup, I encountered the same issue. Looks like a change in deploy-pages github action or something with permissions on github itself.

LeoDiazL commented 10 months ago

Hi @adriansmierciaktsh @pkmelee337, thanks for opening up an issue!

Do you have the following block in your workflow?

permissions:
  contents: read
  pages: write
  id-token: write

You should end with a workflow similar to this:

name: Build and Publish storybook to GitHub Pages

permissions:
  contents: read
  pages: write
  id-token: write

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
    - id: build-publish
      uses: bitovi/github-actions-storybook-to-github-pages@v1.0.1
      with:
        path: storybook-static # change to your build folder
        install_command: npm ci
        build_command: npm run build-storybook

Just in case, have you configured this too?

Let me know if you do, and I'll dig deeper. Thanks!

blaise2s commented 10 months ago

I subscribed to this thread for updates when there was a fix... to keep things moving along, yes, I already had the below block in my workflow file and "GitHub Actions" selected as the source for "Build and deployment" and saw this issue happening this morning.

permissions:
  contents: read
  pages: write
  id-token: write
Screenshot 2023-12-15 at 6 39 30 PM
Akanta21 commented 10 months ago

hi @LeoDiazL

I am facing the same issue here.

Our workflow looks something like this permissions: contents: read pages: write id-token: write

` #👇 Add Storybook build and deploy to GitHub Pages as a step in the workflow
      - id: build-publish
        uses: bitovi/github-actions-storybook-to-github-pages@v1.0.1
        with:
          # default: npm ci
          install_command: npm ci

          # default: npm run build-storybook
          build_command: npm run build:storybook

          # default: dist/storybook
          path: dist/storybook/ui

          # default: true
          checkout: false`

It was working till yesterday

argousiere commented 10 months ago

Encountered the same issue tonight on a new repo. Seems like upgrading the following actions solves the issue:

- actions/upload-pages-artifact@v2.0.0
- actions/deploy-pages@v3

Here is the workflow file of a recent successful run: https://github.com/argousiere/vespertina-ui-react/actions/runs/7233857435/workflow

I copied over some steps from https://github.com/bitovi/github-actions-storybook-to-github-pages/blob/main/action.yaml.

yanachrnsh commented 10 months ago

Facing the same issue. After updating the version to: bitovi/github-actions-storybook-to-github-pages@v1.0.2 have a new error: Error: Unable to resolve action bitovi/github-actions-storybook-to-github-pages@v1.0.2, unable to find version v1.0.2

LeoDiazL commented 10 months ago

@yanachrnsh Try now, just published the new release.

ddanielcruz commented 6 months ago

Upgrading to version bitovi/github-actions-storybook-to-github-pages@v1.0.3 resolved the issue. Here is the successful deployment.