Reference Update Failed on bump

[jaredbarranco]

See below screenshot:

Below is the workflow file that triggers the error:

name: AutoTag SemVer Git Tag
on:
  push:
    branches:
      - main
  workflow_call:
    inputs:
      continue-on-error:
        type: boolean
        required: false
        default: false

jobs:
  bump-tag-version:
    name: Bump and Tag Version
    runs-on: ubuntu-latest
    continue-on-error: ${{inputs.continue-on-error}}
    permissions:
      contents: write
      issues: read
      pull-requests: read
    steps:
      - uses: jefflinse/pr-semver-bump@v1
        name: Bump and Tag Version
        with:
          mode: bump
          repo-token: ${{ secrets.GITHUB_TOKEN }}
          require-release-notes: false
          with-v: true
          base-branch: true
          
      - name: Warn on Failure
        if: failure()
        uses: actions/github-script@v6
        with:
          script: |
            core.warning(`Semantic Version Pip Failed! Check your PR Labels!`);

The explicit permissions are being granted by the calling workflow.

Happy to provide additional information as requested.

[jaredbarranco]

I also updated my workflow to explicitly define the default values like is done in the Readme.md.

Same issue. This is blocking production code pushes for my team.

[jaredbarranco]

Update: I also gave the workflow full write-all permissions for the Github Token. Same error.

The calling workflow is performed on push to my "prod" branch, similar to the example provided in Readme.md

[jaredbarranco]

After digging through the code, I think I've isolated the potential issues to: async function bumpAndTagNewVersion(config)

The error is obviously very cryptic and not directly referenced. It also appears to be an unhandled error as there are several try/catches in the code attempting to provide informative error messages.

[jefflinse]

@jaredbarranco Apologies for failing to follow up on this at the time. Is this still something that needs to be addressed or was this simply from using an outdated version (looking at the related PR)?