Skip to content

GitHub credentials are logged with -vv verbose logging #1426

Closed

Description

@mriedem

Bug Report

Description

Running semantic-release with -vv verbose logging dumps the credentials from the github URL, here I scrubbed it manually:

Feb 4, 2:33:27 PM            DEBUG    Parsing git url                               helpers.py:245
Feb 4, 2:33:27 PM                     'https://x-oauth-basic:[email protected]/IBM-Q-Softw               
Feb 4, 2:33:27 PM                     are/job-prediction-service'    

The issue template asks you to run with -vv and now we have credentials leaked into our CI logs.

Expected behavior

Credentials should be masked in log output.

Actual behavior

Credentials are leaked in verbose output.

Environment

  • Operating System (w/ version): Red Hat UBI
  • Python version: 3.11
  • Pip version: 25.3
  • Semantic-release version: 10.5.3
  • Build tool (w/ version): n/a
pip freeze
Deprecated-1.3.1 MarkupSafe-3.0.3 annotated-types-0.7.0 certifi-2026.1.4 charset_normalizer-3.4.4 click-8.1.8 click-option-group-0.5.9 dotty-dict-1.3.1 gitdb-4.0.12 gitpython-3.1.46 idna-3.11 importlib-resources-6.5.2 jinja2-3.1.6 markdown-it-py-4.0.0 mdurl-0.1.2 pydantic-2.12.5 pydantic-core-2.41.5 pygments-2.19.2 python-gitlab-6.5.0 python-semantic-release-10.5.3 requests-2.32.5 requests-toolbelt-1.0.0 rich-14.3.1 shellingham-1.5.4 smmap-5.0.2 tomlkit-0.13.3 typing-extensions-4.15.0 typing-inspection-0.4.2 urllib3-2.6.3 wrapt-2.0.1

Configuration

Semantic Release Configuration
{
  "semantic_release": {
    "assets": [],
    "branches": {
      "main": {
        "match": "^(main|semantic-release)$",
        "prerelease_token": "rc",
        "prerelease": false
      }
    },
    "changelog": {
      "default_templates":{
        "changelog_file": "CHANGELOG.md"
      },
      "exclude_commit_patterns": [
        "^((?!(feat:|fix:|perf:|build:|chore:|ci:|docs:|style:|refactor:|test:)).)*$"
      ],
      "environment": {
        "block_start_string": "{%",
        "block_end_string": "%}",
        "variable_start_string": "{{",
        "variable_end_string": "}}",
        "comment_start_string": "{#",
        "comment_end_string": "#}",
        "trim_blocks": false,
        "lstrip_blocks": false,
        "newline_sequence": "\n",
        "keep_trailing_newline": false,
        "extensions": [],
        "autoescape": true
      }
    },
    "commit_author": {
      "env": "GIT_COMMIT_AUTHOR",
      "default": "semantic-release <semantic-release>"
    },
    "commit_message": "[skip ci] {version}\n\nAutomatically generated by python-semantic-release",
    "commit_parser": "conventional",
    "logging_use_named_masks": false,
    "major_on_zero": true,
    "remote": {
      "name": "origin",
      "token": {
        "env": "GH_TOKEN"
      },
      "type": "github",
      "ignore_token_for_push": false
    },
    "tag_format": "v{version}",
    "version_variables": [
      "api/version.py:__version__",
      "ci/deployment/k8s/api/Chart.yaml:appVersion",
      "ci/deployment/k8s/workers/Chart.yaml:appVersion"
    ],
    "publish": {
      "dist_glob_patterns": ["dist/*"],
      "upload_to_vcs_release": true
    }
  }
}

Execution Log

It's in #1424 (I split this issue out of that).

Additional context

n/a

Activity

  1. added
    bugSomething isn't working properly
    triagewaiting for initial maintainer review
    on Feb 5, 2026
  2. added
    confirmedPrevent from becoming stale
    and removed
    triagewaiting for initial maintainer review
    on Feb 5, 2026
  3. github-actions commented on May 7, 2026

    @github-actions

    It has been 90 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?

  4. added 13 commits that reference this issue on Jul 3, 2026
    5412473
    c46118f
    0bda440
    f21b238
    b5a9db5
    4128d49
    8d0c124
    a756c4b
    ee0ecc9
    3e61d00
    da0cb2b
    c330284
    811afb0
  5. codejedi365 commented on Jul 4, 2026

    @codejedi365
    Contributor

    🎉 This issue has been resolved in v9.21.2 & v10.6.0 🎉

    You can find more information about this release on the GitHub Releases page.

    If your issue persists, please reply here and we will re-open the issue. If you receive a new error, please open a new issue and reference this issue there.

  6. added and removed
    confirmedPrevent from becoming stale
    needs-updateNeeds status update from maintainers
    on Jul 4, 2026
  7. added theissue type on Jul 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working properlyreleased

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions