Skip to content

fix: fixed release process to use maven publish plugin directly #28

fix: fixed release process to use maven publish plugin directly

fix: fixed release process to use maven publish plugin directly #28

Workflow file for this run

name: Create GitHub Release
on:
pull_request:
types:
- closed
workflow_dispatch:
permissions:
contents: write
### TODO: Replace instances of './.github/workflows/' w/ `auth0/dx-sdk-actions/workflows/` and append `@latest` after the common `dx-sdk-actions` repo is made public.
### TODO: Also remove `get-prerelease`, `get-release-notes`, `get-version`, `maven-publish`, `release-create`, and `tag-exists` actions from this repo's .github/actions folder once the repo is public.
### TODO: Also remove `java-release` workflow from this repo's .github/workflows folder once the repo is public.
jobs:
release:
uses: ./.github/workflows/java-release.yml

Check failure on line 18 in .github/workflows/release.yml

View workflow run for this annotation

GitHub Actions / .github/workflows/release.yml

Invalid workflow file

error parsing called workflow ".github/workflows/release.yml" -> "./.github/workflows/java-release.yml" (source branch with sha:abd641c4fc1563c67d2c4ed9841be2ed5f951336) : every step must define a `uses` or `run` key
with:
java-version: 8.0.402-zulu
secrets:
ossr-username: ${{ secrets.OSSR_USERNAME }}
ossr-token: ${{ secrets.OSSR_TOKEN }}
signing-key: ${{ secrets.SIGNING_KEY }}
signing-password: ${{ secrets.SIGNING_PASSWORD }}
github-token: ${{ secrets.GITHUB_TOKEN }}