Skip to content

Commit

Permalink
chore: someone broke ci and it wasnt me
Browse files Browse the repository at this point in the history
  • Loading branch information
mint-dewit committed Apr 12, 2024
1 parent 8554f60 commit 19eb08f
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/publish-prerelease.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ jobs:
COMMIT_DATE=$(date -d @$COMMIT_TIMESTAMP +%Y%m%d-%H%M%S)
GIT_HASH=$(git rev-parse --short HEAD)
PRERELEASE_TAG=nightly-$(echo "${{ github.ref_name }}" | sed -r 's/[^a-z0-9]+/-/gi')
yarn release:bump-prerelease --no-changelog --no-commit-hooks --preid "$PRERELEASE_TAG-$COMMIT_DATE-$GIT_HASH" prerelease --yes
yarn release:bump-prerelease-ci --no-changelog --no-commit-hooks --preid "$PRERELEASE_TAG-$COMMIT_DATE-$GIT_HASH" prerelease --yes
env:
CI: true
- name: Publish to NPM
Expand Down
3 changes: 2 additions & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@
"release:set-version": "lerna version --exact --no-changelog --no-push --yes && yarn fix-version",
"release:bump-release": "lerna version --exact --conventional-commits --conventional-graduate --tag-version-prefix='v' --no-push --force-publish='*' && yarn fix-version",
"release:bump-prerelease": "lerna version --exact --conventional-commits --conventional-prerelease --tag-version-prefix='v' --no-push --force-publish='*' && yarn fix-version",
"release:bump-prerelease-ci": "lerna version --exact --conventional-commits --conventional-prerelease --tag-version-prefix='v' --no-push --force-publish='*' && yarn fix-version",
"fix-version": "node scripts/fix-version.js",
"setup": "lerna bootstrap",
"reset": "node scripts/reset.js",
Expand Down Expand Up @@ -49,4 +50,4 @@
},
"prettier": "@sofie-automation/code-standard-preset/.prettierrc.json",
"packageManager": "[email protected]"
}
}

0 comments on commit 19eb08f

Please sign in to comment.