question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

failing to recognize the current version and always cutting a major release

See original GitHub issue

The problem

Semantic release is failing to recognize the current version and always cutting a major release

  • python-semantic-release 7.19.2

Expected behavior

Should recognize that the tag exists and apply the appropriate version

Additional context

Output log

[2021-09-27T20:13:21.771Z] debug: get_current_version_by_config_file()
[2021-09-27T20:13:21.771Z] debug: Parsing current version: path=PosixPath('kong_bench/__init__.py') pattern='__version__ *[:=] *["\\\'](\\d+\\.\\d+(?:\\.\\d+)?)["\\\']' num_matches=1
[2021-09-27T20:13:21.771Z] debug: Regex matched version: 13.0.0
[2021-09-27T20:13:21.771Z] debug: get_current_version_by_config_file -> 13.0.0
[2021-09-27T20:13:21.771Z] debug: evaluate_version_bump('13.0.0', None)
[2021-09-27T20:13:21.771Z] debug: Reference v13.0.0 does not exist, considering entire history
[2021-09-27T20:13:21.771Z] debug: parse_commit_message('fix(ci): A fix a version variable for semantic-release
[2021-09-27T20:13:21.771Z] debug: 
[2021-09-27T20:13:21.771Z] debug: adds the version variable parameter to the main module init file

Remote tags

git tag

v1.0.0
v10.0.0
v11.0.0
v12.0.0
v13.0.0
v2.0.0
v3.0.0
v4.0.0
v5.0.0
v6.0.0
v6.0.1
v7.0.0
v8.0.0
v9.0.0

release config

[tool.semantic_release]
version_toml = "pyproject.toml:tool.poetry.version"
version_variable = "kong_bench/__init__.py:__version__"
branch = "main"
build_command = "poetry build"
upload_to_pypi = false
dist_path = "dist"
commit_subject = "release: Version {version} [skip ci]"
commit_author = "LogDNA Bot <bot@logdna.com>"

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:11 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
esatterwhitecommented, Dec 21, 2021

Semantic release uses tags, that’s how it understands the previous version. If it can’t resolve the last version via repo tags, which it creates, it will assume no previous version and cut a major

0reactions
github-actions[bot]commented, Nov 14, 2022

This bug report has been labelled as help wanted since there has been no activity in the last 3 weeks. It will not be closed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Breaking Benjamin - Failure (Audio Only) - YouTube
Breaking Benjamin latest album DARK BEFORE DAWN featuring the singles “ Failure,” “Angels Fall,” and “Ashes of Eden” is available now!
Read more >
1910.1200 - Hazard Communication.
The purpose of this section is to ensure that the hazards of all chemicals produced or imported are classified, and that information concerning...
Read more >
Still The No. 1 Rule For Stock Market Investors: Always Cut ...
Cutting losses quickly prevents you from suffering a devastating fall that's too steep to recover from.
Read more >
Helix 3.50 Release Notes - HELIX/HX - Line 6 Community
Helix/HX 3.50 (released November 3, 2022) includes 24 new cabs running on an all new cab engine, 5 new amps, 7 new effects,...
Read more >
The 20 Most Successful Technology Failures of All Time
Some failed gadgets and software weren't buried away to be forgotten. Instead, they laid the groundwork for more fully-formed ideas.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found