Closed alexgg closed 2 years ago
Testing details:
balena-versionist
modify it to depend on ag-versionist
and deploy an npm package
name: Run versionist
on:
push:
branches:
- master
jobs:
versionist: name: Run versionist if: "!contains(github.event.head_commit.author.name, 'versionist')" # Ignore push events made by the service account runs-on: ubuntu-latest outputs: # (optional) Only if you want to use them in next jobs version: ${{ steps.versionist.outputs.version }} # version: project's version after running versionist updated: ${{ steps.versionist.outputs.updated }} # updated: true if the version has been updated steps:
github_email: 'yoctocookbook2ndedition@lindusembedded.com'
github_username: 'yoctocookbook2ndedition'
github_token: ${{ secrets.GH_VERSIONIST_TOKEN }}
With the above, the device repostiory dependencies are updated and the changelog is nested correctly.
@balena-ci I self-certify!
The nested changelog support currently needs to be provided with the version range on the commit body, similarly to:
Update from to
This is cumbersome and does not work well with tools that automatically update submodule dependencies like renovatebot.
This commit keeps the legacy behaviour but will extract the version range from git metadata when not provided. This new behaviour can be used by specifyng a commit body similar to:
Update
Change-type: patch Signed-off-by: Alex Gonzalez alexg@balena.io