Failed with 404 "discussion category unmatch"

[harrymkt]

Code:

- name: Release
  uses: softprops/action-gh-release@v2
  with:
    files: |
      file1
      file2
    draft: false

As you can see, I'm not even using discussion_category_name input.

[DasBen]

Did you find a fix? I have the same problem. Tried downgrading to v0.1.15 or upgrading to v2.2.1 but did not help.

Example Logs:

Run softprops/action-gh-release@v2
  with:
    body_path: .github/templates/release_template_npmlib.md
    files: ./src/.generated/sbom.json
  
  
  
    generate_release_notes: true
    name: 2.0.5
    tag_name: 2.0.5
    target_commitish: XXX
    token: ***
  env:
    ACTIONS_PATH: XXX
    AWS_DEFAULT_REGION: eu-central-1
    AWS_REGION: eu-central-1
    AWS_ACCESS_KEY_ID: ***
    AWS_SECRET_ACCESS_KEY: ***
    JIRA_CLOUD_URL: ***
    TOKEN: ***
    MCBSTEST_JIRACLOUD_CREDENTIALS: ***
    NPM_CONFIG_USERCONFIG: /home/runner/work/_temp/.npmrc
    NODE_AUTH_TOKEN: XXXXX-XXXXX-XXXXX-XXXXX
  
👩‍🏭 Creating new GitHub release for tag 2.0.5 using commit "XXX"...
⚠️ GitHub release failed with status: 404
{"message":"Not Found","documentation_url":"https://docs.github.com/rest/releases/releases#create-a-release","status":"404"}
Skip retry - discussion category mismatch
Error: Not Found - https://docs.github.com/rest/releases/releases#create-a-release

[harrymkt]

Did you find a fix? I have the same problem. Tried downgrading to v0.1.15 or upgrading to v2.2.1 but did not help.

I found that this is happening on private repositories. I haven't tried with draft set to false though.

[DasBen]

I could fix it for my side.

For me the error message was wrong. GitHub should have told me, that the provided token is wrong or has insufficient permissions.

It might help you to try create a PAT with enough permissions, setting it in the repository as secret and then providing it to the action through "secrets.TOKEN"

[harrymkt]

It might help you to try create a PAT with enough permissions, setting it in the repository as secret and then providing it to the action through "secrets.TOKEN"

Of course I always use PAT.

token: ${{ secrets.TK }}