Using GITHUB_TOKEN should be possible now

[TheMeier]

For me using this worked:

jobs:
  renovate:
    permissions:
      contents: read
      issues: read
      pull-requests: write
      repository-projects: read
      statuses: read
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4.1.6
      - name: Renovate
        uses: renovatebot/github-action@v40.1.11
        with:
          configurationFile: renovate-config.json
          token: ${{ secrets.GITHUB_TOKEN }}

Note the permissions section. Maybe that is related to #796

[viceice]

Converted to discussion because there is nothing in the description which can be actioned on.

[viceice]

In your case the actions from pusched branches and opened PRs won't be triggered, so it doesn't work as espected¹

Footnotes

1. /~https://github.com/renovatebot/github-action?tab=readme-ov-file#token ↩

[TheMeier]

Yeah about that sections, I wonder if it could be a bit more elaborate. I don't really understand what it is saying

[viceice]

if you push with secrets.GiTHUB_TOKEN then no action on that branch / PR will be triggered. You should follow the link¹ there.

Footnotes

1. https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow ↩

[TheMeier]

Uhm in my test it did just that, create a PR and the tests were run:
TheMeier/puppet-prometheus#14

[TheMeier]

Oh because i have workflow:dispatch

[viceice]

please provide a full working workflow

[TheMeier]

never mind, turned out i did overlook something, not sure what though