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.

7.0.0 tag is not part of any branch

See original GitHub issue

The 7.0.0 tag in this repo is not part of any branch:

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository. 7.0.0

git log --all --graph reveals:

| | * commit 3554b833c24f541af5c7272e47cfa52b89d8138d (tag: 7.0.0, upstream/release-7.0.0, origin/pr/9598, refs/pullreqs/9598, release-7.0.0)
| | | Author: Florian Bruhin <me@the-compiler.org>
| | | Date:   Thu Feb 3 12:31:36 2022 +0100
| | | 
| | |     Add note to changelog
| | | 
| | * commit 6ea7f990a040cacfbc671a8c29f2d76533d9d523
| |/  Author: pytest bot <pytestbot@gmail.com>
|/|   Date:   Thu Feb 3 16:08:04 2022 +0000
| |   
| |       Prepare release version 7.0.0

but that was then squash-merged, which means there is now a new commit which is not the tagged one…

This means that, for example, git describe --abbrev=0 --tags returns 7.0.0.dev0, causing a wrong author list in #9654. It’s also somewhat questionable from a trust perspective…

So we might want to remove the tag, reapply it at e37fbe5685d330cbe7819c5a08d0a524df7299bf (same content, different commit) and finally change the release instructions to mention that the release PR should not be squash-merged?

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
The-Compilercommented, Feb 9, 2022

Tag pushed: https://github.com/pytest-dev/pytest/tree/7.0.0.post1

For some reason I don’t quite understand, I don’t seem to see an action running for it. Fingers crossed that we don’t suddenly see a new PyPI release out of nowhere.

See #9657 for the docs change.

1reaction
bluetechcommented, Feb 9, 2022

Can just cancel the action real quick 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

Releasing on a maintenance branch causes tag errors #1038
Hi,. I am using the new beta to support maintenance branch - I am currently testing it. I created a branch from the...
Read more >
git - list tags contained by a branch - Stack Overflow
No, git describe will only list one tag/ref. – sleske. Mar 1, 2016 at 9:31. Add a comment ...
Read more >
setuptools-scm - PyPI
A Python regex string to extract the version part from any SCM tag. The regex needs to contain either a single match group,...
Read more >
SD-WAN configurations for steering traffic from the hub to the ...
Because all branches advertise the same community strings and route-tags, only one set of service rules is required for all of the branches,...
Read more >
Cisco Firepower Release Notes, Version 7.0 - Security
Policy deployment fails with error- Rule update is running but there are no updates in progress. CSCwb56905. ASA blocking 0.0.0.0 IP and netmask...
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