tagging a release creates a directory 0.11. instead of 0.11.0
See original GitHub issue🐛 Bug
The script to commit new docs when the repo is tagged is faulty. It assumes the tag is 5 characters, which is fine when the tag is 0.9.0
but fails for 0.10.0
. This is the problematic line https://github.com/pytorch/text/blob/main/.circleci/config.yml.in#L589
After changing it, the actual config.yml
should be regenerated with regenerate.py
.
@brianjo: this is probably the cause of this problem in the other domain libraries as well.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
tag already exists in the remote" error after recreating the git tag
9 Answers 9 · Go to tab Repository -> Tag -> Remove Tag · Select the conflicting tag name · Check Remove tag...
Read more >Release 0.11.0 · Issue #1110 · go-kit/kit - GitHub
Yes, a new release is in order. Your list looks pretty good, although I think we should consider a two release sequence. First...
Read more >call from Powershell with --assets-link does not work ... - GitLab
I'm facing a similar problem while trying to create a release using the ci release keyword as documented. I'm using release-cli version 0.11.0...
Read more >Git: The Difference Between Lightweight and Annotated Tags
Annotated tags: A tag that has its own commit hash and is, as such, stored as a separate object in git. This tag...
Read more >Upgrading to CDKTF Version 0.11 | Terraform
0.11 includes improvements to the provider code bindings, to allow referencing maps of computed attributes as a whole map instead of just individual...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@malfet opened PRs against all the repos. Sorry for the mess.
If the tag is
v0.11.3rc2
and I only want0.11.3
, I will need something more complicated thancut