Skip to content

Commit

Permalink
fix npm release workflow (#826)
Browse files Browse the repository at this point in the history
fixes npm release workflow

releases were not happening because of wrong relative path to action
files in `npm-release.yml` workflow file.
  • Loading branch information
tusharpandey13 authored Jan 21, 2025
2 parents 88f9ddb + dc602a8 commit 047e766
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions .github/workflows/npm-release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ on:
required: true
type: string
require-build:
default: true
default: "true"
type: string
release-directory:
default: './'
Expand All @@ -32,17 +32,17 @@ jobs:

# Get the version from the branch name
- id: get_version
uses: ./get-version
uses: ./.github/actions/get-version

# Get the prerelease flag from the branch name
- id: get_prerelease
uses: ./get-prerelease
uses: ./.github/actions/get-prerelease
with:
version: ${{ steps.get_version.outputs.version }}

# Get the release notes
- id: get_release_notes
uses: ./get-release-notes
uses: ./.github/actions/get-release-notes
with:
token: ${{ secrets.github-token }}
version: ${{ steps.get_version.outputs.version }}
Expand All @@ -51,7 +51,7 @@ jobs:

# Check if the tag already exists
- id: tag_exists
uses: ./tag-exists
uses: ./.github/actions/tag-exists
with:
tag: ${{ steps.get_version.outputs.version }}
token: ${{ secrets.github-token }}
Expand All @@ -61,7 +61,7 @@ jobs:
run: exit 1

# Publish the release to our package manager
- uses: ./npm-publish
- uses: ./.github/actions/npm-publish
with:
node-version: ${{ inputs.node-version }}
require-build: ${{ inputs.require-build }}
Expand All @@ -70,7 +70,7 @@ jobs:
release-directory: ${{ inputs.release-directory }}

# Create a release for the tag
- uses: ./release-create
- uses: ./.github/actions/release-create
with:
token: ${{ secrets.github-token }}
name: ${{ steps.get_version.outputs.version }}
Expand Down

0 comments on commit 047e766

Please sign in to comment.