Address invalid vocabulary release credentials

[Copilot]

The workflow failed while creating a release in FinOMOP_vocabularies: GitHub rejected the configured TOKEN_FINOMOP_VOCABULARIES credential. Validation and dashboard deployment completed successfully.

• Required configuration: Refresh the TOKEN_FINOMOP_VOCABULARIES repository secret with a valid token authorized to create releases in FinOMOP_vocabularies.
• Repository changes: None; this authentication failure cannot be corrected safely in workflow code.

[javier-gracia-tabuenca-tuni]

this is the error

Run softprops/action-gh-release@v1
  with:
    tag_name: 48
    name: development - 48 - bec615a98a1fb29361d0ac8d730f357c324a76d0
    body: Automated release from FinOMOP_mappings workflow.
    files: ./output_data/FinOMOP_vocabularies.zip
    draft: true
    prerelease: true
    repository: FinOMOP/FinOMOP_vocabularies
    token: ***
  env:
    BUILD_DASHBOARD: true
    BUILD_VOCABULARIES: true
    GITHUB_PAT: ***
    R_LIBS_USER: /home/runner/work/_temp/Library
    TZ: UTC
    _R_CHECK_SYSTEM_CLOCK_: FALSE
    NOT_CRAN: true
    RSPM: https://packagemanager.posit.co/cran/__linux__/noble/latest
    RENV_CONFIG_REPOS_OVERRIDE: https://packagemanager.posit.co/cran/__linux__/noble/latest
    FINAL_STATUS: WARNING
(node:26243) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:26243) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
⚠️ Unexpected error fetching GitHub release for tag refs/heads/development: HttpError: Bad credentials

I think it is bcs one of in gh action one of the refered action is deprecated
@copilot

[Copilot]

this is the error

Run softprops/action-gh-release@v1

...

The Node 20 deprecation notice is separate from the failure. The release action starts and reaches GitHub’s API, which rejects its configured token with Bad credentials; switching action versions would not repair that credential. The rerun (attempt 2) on the same development run failed identically at the release step, while validation and Pages deployment succeeded. Please check that TOKEN_FINOMOP_VOCABULARIES is current and authorized for FinOMOP/OMOP_vocabularies (for a fine-grained token, grant Contents: write), then rerun.