semantic-release / semantic-release/github
steps.semantic.outputs.release-version & steps.semantic.outputs.new-release-published is empty
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
Hi,
This my semantic release yml file but its not version and new-release published as true.
`steps:
- uses: actions/checkout@v2
- name: create version doc
run: |
echo "{git-sha: "$(git log -1 --format="%H")",version: "$(git ls-remote --tags --sort='v:refname' | tail -n1 | sed 's/.*///; s/^{}//')"}" > ./public/aavplus/version.json
cat ./public//version.json
- uses: actions/setup-node@v1
with:
node-version: 16.x
- name: validate before release
run: |
npx --yes npm@8.5.5 ci --no-save
npm run build
env:
NPM_PKG_TOKEN: ${{ secrets.NPM_PKG_TOKEN }}
CI: true
- name: semantic release
run: npx semantic-release@19.0.5
id: semantic
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: update version doc
run: |
echo "$NEW_CHANGE"
echo $NEW_CHANGE
echo ${{ steps.semantic.outputs.new-release-published }}
echo "{git-sha: \"$(git log -1 --format="%H")\",version: \"$VERSION_TAG\"}" > ./public/aavplus/version.json
cat ./public//version.json
env:
VERSION_TAG: v${{ steps.semantic.outputs.release-version }}. ---> **Empty**
NEW_CHANGE: ${{ steps.semantic.outputs.new-release-published }}` --> **Empty**
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the workflow's semantic step running npx semantic-release@19.0.5 and the later references to steps.semantic.outputs.release-version and new-release-published. Check the repository's documented or implemented outputs first; done means determining whether these values are supported and, if so, reproducing and correcting the empty-output behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100