Skip to content

Logs are too verbose #1447

Open
#1473
Open
Logs are too verbose#1447
#1473
Labels
bugSomething isn't working properlyconfirmedPrevent from becoming staleneeds-updateNeeds status update from maintainers

Description

@jontwo
jontwo
opened on Jul 3, 2026

Bug Report

Description

We've just upgraded from v9.8.0 to v10.5.3 and with the same semantic-release -v version there are no so many logs, Gitlab stops collecting them.

2026-07-03T08:35:23.145038Z 01O 
2026-07-03T08:35:23.145039Z 01O no changes added to commit (use "git add" and/or "git commit -a")
2026-07-03T08:35:23.145483Z 01O �[32;1m$ semantic-release -v version --skip-build --no-commit --no-tag --no-changelog�[0;m
2026-07-03T08:35:23.679095Z 01E [08:35:23] INFO     Loading configuration from pyproject.toml         util.py:77
2026-07-03T08:35:23.775061Z 01E            INFO     Using group 'main' options, as 'main' matches  config.py:590
2026-07-03T08:35:23.775066Z 01E                     'main'                                                      
2026-07-03T08:35:23.778462Z 01E            INFO     Repository is a shallow clone, converting to  version.py:515
2026-07-03T08:35:23.778466Z 01E                     full clone...                                               
2026-07-03T08:35:23.779721Z 01E            INFO     Converting shallow clone to full clone...  gitproject.py:115
2026-07-03T08:35:27.050482Z 01E [08:35:27] INFO     Repository unshallowed successfully        gitproject.py:117
2026-07-03T08:35:27.051250Z 01E            INFO     changes will not be pushed because            version.py:520
2026-07-03T08:35:27.051253Z 01E                     --no-commit disables pushing                                
2026-07-03T08:35:27.052010Z 01E            INFO     No vcs release will be created because        version.py:530
2026-07-03T08:35:27.052011Z 01E                     pushing changes is disabled                                 
2026-07-03T08:35:27.077002Z 01E            INFO     found 2006 previous tags                     algorithm.py:60
2026-07-03T08:35:27.821600Z 01E            INFO     The last full version in this branch's      algorithm.py:298
2026-07-03T08:35:27.821629Z 01E                     history was 39.5.5                                          
2026-07-03T08:35:27.822416Z 01E            INFO     The latest release in this branch's history algorithm.py:328
2026-07-03T08:35:27.822418Z 01E                     was 39.5.5                                                  
2026-07-03T08:35:27.877042Z 01E            INFO     Found 2 commits since the last release!     algorithm.py:340
2026-07-03T08:35:27.878080Z 01E            INFO     The type of the next release release is:    algorithm.py:384
2026-07-03T08:35:27.878083Z 01E                     major                                                       
2026-07-03T08:35:27.879506Z 01O 40.0.0
2026-07-03T08:35:27.904834Z 01E            INFO     found 2006 previous tags                     algorithm.py:60
2026-07-03T08:35:27.945180Z 01E            INFO     found 2006 previous tags                     algorithm.py:60
2026-07-03T08:35:27.982093Z 01E            INFO     found 2006 previous tags                     algorithm.py:60
2026-07-03T08:35:28.264998Z 01E [08:35:28] INFO     parsing commit [f6caf9d0] Merge       release_history.py:111
2026-07-03T08:35:28.265004Z 01E                     branch '3450_pathlib_decorator' into                        
2026-07-03T08:35:28.265005Z 01E                     'main'  fix                                                 
2026-07-03T08:35:28.265938Z 01E            INFO     Excluding merge commit[f6caf9d]       release_history.py:167
2026-07-03T08:35:28.266964Z 01E            INFO     parsing commit [608296f6] fix!:       release_history.py:111
2026-07-03T08:35:28.266967Z 01E                     jbafarm (gismo#3450 gismo#3468) use                         
2026-07-03T08:35:28.266968Z 01E                     pathlib deco                                                
2026-07-03T08:35:28.267945Z 01E            INFO     [Unreleased] adding commit[608296f]   release_history.py:200
2026-07-03T08:35:28.267947Z 01E                     to unreleased 'bug fixes'                                   
2026-07-03T08:35:28.269910Z 01E            INFO     parsing commit [919f227c] 39.5.5      release_history.py:111
2026-07-03T08:35:28.269914Z 01E                     Automatically generated by                                  
2026-07-03T08:35:28.269915Z 01E                     python-semantic-rel                                         
2026-07-03T08:35:28.270769Z 01E            INFO     Excluding  commit[919f227] 39.5.5     release_history.py:175
2026-07-03T08:35:28.271736Z 01E            INFO     parsing commit [587807ca] Merge       release_history.py:111
2026-07-03T08:35:28.271738Z 01E                     branch 'coastal_flood_warning_error'                        
2026-07-03T08:35:28.271739Z 01E                     into 'main'                                                 
2026-07-03T08:35:28.272511Z 01E            INFO     Excluding merge commit[587807c]       release_history.py:167
2026-07-03T08:35:28.273518Z 01E            INFO     parsing commit [ee90e9d6] fix:        release_history.py:111
2026-07-03T08:35:28.273519Z 01E                     coastal_flood (3440) fixed warning                          
2026-07-03T08:35:28.273520Z 01E                     error                                                       
2026-07-03T08:35:28.274477Z 01E            INFO     [39.5.5] adding commit[ee90e9d] to    release_history.py:208
2026-07-03T08:35:28.274479Z 01E                     release 'bug fixes'                                         
2026-07-03T08:35:28.276017Z 01E            INFO     parsing commit [2ab1eb04] 39.5.4      release_history.py:111
2026-07-03T08:35:28.276020Z 01E                     Automatically generated by                                  
2026-07-03T08:35:28.276021Z 01E                     python-semantic-rel                                         
2026-07-03T08:35:28.277571Z 01E            INFO     Excluding  commit[2ab1eb0] 39.5.4     release_history.py:175
2026-07-03T08:35:28.278531Z 01E            INFO     parsing commit [763fead5] Merge       release_history.py:111
2026-07-03T08:35:28.278534Z 01E                     branch '115_semantic_release' into                          
2026-07-03T08:35:28.278535Z 01E                     'main'  fix:                                                
2026-07-03T08:35:28.279309Z 01E            INFO     Excluding merge commit[763fead]       release_history.py:167
2026-07-03T08:35:28.280260Z 01E            INFO     parsing commit [361e600a] fix: ci     release_history.py:111
2026-07-03T08:35:28.280262Z 01E                     (shared-repo-group#115) try new                             
2026-07-03T08:35:28.280263Z 01E                     semantic-relea                                              
2026-07-03T08:35:28.281269Z 01E            INFO     [39.5.4] adding commit[361e600] to    release_history.py:208
2026-07-03T08:35:28.281272Z 01E                     release 'bug fixes'                                         
2026-07-03T08:35:28.282876Z 01E            INFO     parsing commit [321afcb2] 39.5.3      release_history.py:111
2026-07-03T08:35:28.282881Z 01E                     Automatically generated by                                  
2026-07-03T08:35:28.282882Z 01E                     python-semantic-rel                                         
2026-07-03T08:35:28.283724Z 01E            INFO     Excluding  commit[321afcb] 39.5.3     release_history.py:175
2026-07-03T08:35:28.284637Z 01E            INFO     parsing commit [8903cd19] Merge       release_history.py:111
2026-07-03T08:35:28.284639Z 01E                     branch '3463_attribute_key_error'                           
2026-07-03T08:35:28.284640Z 01E                     into 'main'  f                                              
2026-07-03T08:35:28.285414Z 01E            INFO     Excluding merge commit[8903cd1]       release_history.py:167
2026-07-03T08:35:28.286367Z 01E            INFO     parsing commit [dedd97ce] fix:        release_history.py:111
2026-07-03T08:35:28.286370Z 01E                     attribute_esl_points (3463) added                           
2026-07-03T08:35:28.286371Z 01E                     check for exist                                             
2026-07-03T08:35:28.287385Z 01E            INFO     [39.5.3] adding commit[dedd97c] to    release_history.py:208
2026-07-03T08:35:28.287387Z 01E                     release 'bug fixes'                                         

...

2026-07-03T08:35:53.200127Z 01E            INFO     parsing commit [7d90b766] 32.4.5      release_history.py:111
2026-07-03T08:35:53.200130Z 01E                     Automatically generated by                                  
2026-07-03T08:35:53.200131Z 01E                     python-semantic-rel                                         
2026-07-03T08:35:53.200943Z 01E            INFO     Excluding  commit[7d90b76] 32.4.5     release_history.py:175
2026-07-03T08:35:53.202041Z 01E            INFO     parsing commit [a8e84a34] Merge       release_history.py:111
2026-07-03T08:35:53.202043Z 01E                     branch '2982_frog' into 'main'  fix:                        
2026-07-03T08:35:53.202044Z 01E                     flood_repor                                                 
2026-07-03T08:35:53.202818Z 01E            INFO     Excluding merge commit[a8e84a3]       release_history.py:167
2026-07-03T08:35:53.203760Z 01E            INFO     parsing commit [fb0906a0] fix:        release_history.py:111
2026-07-03T08:35:53.203763Z 01E                     flood_report_generator (gismo#2982)                         
2026-07-03T08:35:53.203764Z 01E                     Import frog t                                               
2026-07-03T08:35:53.204745Z 01E            INFO     [32.4.5] adding commit[fb0906a] to    release_history.py:208
2026-07-03T08:35:53.204747Z 01E                     release 'bug fixes'                                         
2026-07-03T08:35:53.205718Z 01E            INFO     parsing commit [8facf8c3] Merge       release_history.py:111
2026-07-03T08:35:53.205721Z 01E                     branch '2205_numpy2' into 'main'                            
2026-07-03T08:35:53.205722Z 01E                     chore: jbafarm                                              
2026-07-03T08:35:53.206472Z 01E            INFO     Excluding merge commit[8facf8c]       release_history.py:167
2026-07-03T08:35:53.208579Z 01E            INFO     parsing commit [4ede69f3] chore:      release_history.py:111
2026-07-03T08:35:53.208581Z 01E                     jbafarm (gismo#2205) numpy2                                 
2026-07-03T08:35:53.208582Z 01E                     compatibility                                               
2026-07-03T08:35:53.210870Z 01E            INFO     [32.4.5] adding commit[4ede69f] to    release_history.py:208
2026-07-03T08:35:53.210873Z 01E                     release 'chores'                                            
2026-07-03T08:35:53.214138Z 01E            INFO     parsing commit [222f783a] 32.4.4      release_history.py:111
2026-07-03T08:35:53.214143Z 01E                     Automatically generated by                                  
2026-07-03T08:35:53.214170Z 01E                     python-semantic-rel                                         
2026-07-03T08:35:53.216058Z 01E            INFO     Excluding  commit[222f783] 32.4.4     release_history.py:175
2026-07-03T08:35:53.217558Z 01E            INFO     parsing commit [89b593a0] Merge       release_history.py:111
2026-07-03T08:35:53.217561Z 01E                     branch '3022_coastal_flood_fix_test'                        
2026-07-03T08:35:53.217562Z 01E                     into 'main'                                
�[33;1mJob's log exceeded limit of 4194304 bytes.
Job execution will continue but no more output will be collected.�[0;m

Expected behavior

The amount of logging should be short enough to be displayed. Gitlab stops collecting at ~4500 lines, but the last job before we upgraded was 528 lines.

Actual behavior

There is too much logging for the pipeline to store it all.

Environment

  • Operating System (w/ version): Running in ghcr.io/astral-sh/uv:python3.12-bookworm
  • Python version: 3.12
  • Pip version: 26.1.2
  • Semantic-release version: 10.5.3
  • Build tool (w/ version): Not known (running in CI)
pip freeze

We're running in CI, so here's the pip install output

Successfully installed Deprecated-1.3.1 MarkupSafe-3.0.3 annotated-types-0.7.0 certifi-2026.6.17 charset_normalizer-3.4.7 click-8.1.8 click-option-group-0.5.9 dotty-dict-1.3.1 gitdb-4.0.12 gitpython-3.1.50 idna-3.18 importlib-resources-6.5.2 jinja2-3.1.6 markdown-it-py-4.2.0 mdurl-0.1.2 pydantic-2.13.4 pydantic-core-2.46.4 pygments-2.20.0 python-gitlab-6.5.0 python-semantic-release-10.5.3 requests-2.34.2 requests-toolbelt-1.0.0 rich-14.3.4 shellingham-1.5.4 smmap-5.0.3 tomlkit-0.13.3 typing-extensions-4.16.0 typing-inspection-0.4.2 urllib3-2.7.0 wrapt-2.2.2

git log --oneline --decorate --graph --all -n 50

Configuration

Semantic Release Configuration 








Build System Configuration









GitHub Actions Job Definition





Execution Log




semantic-release -vv command







Additional context


Activity
  1. jontwo
    added 
    bugSomething isn't working properly
     
    triagewaiting for initial maintainer review
     on Jul 3, 2026
  2. codejedi365
    added 
    confirmedPrevent from becoming stale
     and removed 
    triagewaiting for initial maintainer review
     on Jul 3, 2026
  3. codejedi365 commented on Jul 3, 2026 
    @codejedi365
    codejedi365
    on Jul 3, 2026
    Contributor
    Unfortunately logs are proportional to the size of the repository and looks like yours is quite massive (2006 tags, ? Commits). Sorry this occurred for you as I actually cut logs but obviously increased them somewhere else.
    

    Will consider what can move to -vv vs -v, and maybe how to just provide enough detail without any verbosity.
  4. jontwo commented on Jul 8, 2026 
    @jontwo
    jontwo
    on Jul 8, 2026
    Author
    Yeah, it's been going since 2016 or so, there are quite a few commits and tags now! We can always drop the -v if needed, but it's good to have a bit of detail for when it all goes wrong.
  5. codejedi365 commented on Jul 8, 2026 
    @codejedi365
    codejedi365
    on Jul 8, 2026
    Contributor
    Can you provide the number of commits (and time it takes to run) so I understand the scale. There is one issue (#722) already that discusses performance with ~3K commits and I have already release some significant improvements to performance and planning on more in the future. PSR uses itself to release and we are reaching 2K commits but our time behavior has been reasonable so I'm curious for yours as well.
  6. jontwo commented on Jul 8, 2026 
    @jontwo
    jontwo
    on Jul 8, 2026
    Author
    Here's the information on the repo front page. The CI pipeline is set to only do a shallow clone of the last 20 commits though, so semantic-release shouldn't be going all the way back through them.
    

    7,920 Commits
62 Branches
2,046 Tags
137.8 GiB Project Storage
778 Releases

    

    I can't tell exactly how long it takes, but the entire job is about 2m20 and setup about 1m20 of that. Given the messages that are in the log, it looks like the tool is looking at every tag, not just the tags on the last 20 commits.
  7. codejedi365 commented on Jul 11, 2026 
    @codejedi365
    codejedi365
    on Jul 11, 2026
    Contributor
    

    Here's the information on the repo front page.
    

    

    Thanks! It's rather quicker than I anticipated.
    

    

    The CI pipeline is set to only do a shallow clone of the last 20 commits though, so semantic-release shouldn't be going all the way back through them.
    

    

    That would be nice wouldn't it? Well in v10, PSR automatically unshallows the repo because it causes too many inconsistency errors and it's not in PSRs best interest to try to figure it out incrementally. To facilitate changelog generation, PSR must review every commit (all 7K) at runtime so it can regenerate the changelog if it doesn't exist.
    

    

    Given the messages that are in the log, it looks like the tool is looking at every tag, not just the tags on the last 20 commits.
    

    

    Similar to above and more of a git limitation but all tags must be reviewed so that we know when we have hit a tag in the tree traversal. The unfortunate part is we actually parse all tags twice because the legacy code did not cache the result. I did not write or design this portion but I have been working on significant improvements to the core algorithm to increase performance.
  8. github-actions commented on Oct 9, 2026 
    @github-actions
    github-actionsbot
    on Oct 9, 2026 – with 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?
  9. github-actions
    added 
    needs-updateNeeds status update from maintainers
     on Oct 9, 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 properlyconfirmedPrevent from becoming staleneeds-updateNeeds status update from maintainers
    Type
    No type
    Projects
    No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions