[Dev] Revert mistakenly pushed RC tags

[amoeba]

Describe the enhancement requested

I mistakenly force-pushed all tags rather than just the tag I intended (r-universe-release) and saw two RC tags got updated and a few other tags got created. I think the extra tags need to be deleted and the RC tags need to be reverted back to point to their original commit. I'm filing an issue for visibility.

$ git push --force --tags
Enumerating objects: 38, done.
Counting objects: 100% (38/38), done.
Delta compression using up to 14 threads
Compressing objects: 100% (18/18), done.
Writing objects: 100% (20/20), 3.54 KiB | 3.54 MiB/s, done.
Total 20 (delta 19), reused 3 (delta 2), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (19/19), completed with 18 local objects.
To https://github.com/apache/arrow
 + f0d3a454bd...a8a979a41b apache-arrow-19.0.0-rc0 -> apache-arrow-19.0.0-rc0 (forced update)
 + d05ba772c3...6a6bec0fa7 apache-arrow-20.0.0-rc0 -> apache-arrow-20.0.0-rc0 (forced update)
 + b1ebcdb797...d0a0a8add6 r-universe-release -> r-universe-release (forced update)
 * [new tag]               list -> list
 * [new tag]               show -> show
 * [new tag]               test-release-rc2 -> test-release-rc2
 * [new tag]               vtest -> vtest
 * [new tag]               vtesting -> vtesting

I deleted all of the "[new tag]" tags on GitHub already but I now want to delete, re-tag, and push these tags:

• apache-arrow-19.0.0-rc0 should be tagged on f0d3a454bd
• apache-arrow-20.0.0-rc0 should be tagged on d05ba772c3

@assignUser @kou @raulcd could any of you double-check me here?

Component(s)

Developer Tools

[assignUser]

I see 400b068b45aa06160963e8de2c21d026dbe0d4ac for 19 rc0 and 107c6b1cd1cbb5395f1520fe13f79c7fb52009bd for 20 rc0

[amoeba]

Thanks @assignUser. Those would make sense given the commit referenced in each of the respective verification PRs,

• 19.0.0-RC0: WIP: [Release] Verify release-19.0.0-rc0 #45224
• 20.0.0-RC0: WIP: [Release] Verify release-20.0.0-rc0 #46064

I'd like to know why both commits I saw were different but maybe that'll just remain a mystery. Should I go ahead and fix the tags?

[amoeba]

I'd run,

git tag -d apache-arrow-19.0.0-rc0
git tag -a "apache-arrow-19.0.0-rc0" -m "[Release] Apache Arrow Release 19.0.0 RC0" 400b068b45aa06160963e8de2c21d026dbe0d4ac
git tag -d apache-arrow-20.0.0-rc0
git tag -a "apache-arrow-20.0.0-rc0" -m "[Release] Apache Arrow Release 20.0.0 RC0" 107c6b1cd1cbb5395f1520fe13f79c7fb52009bd
# apache is my remote for apache/arrow
git push --force apache apache-arrow-19.0.0-rc0
git push --force apache apache-arrow-20.0.0-rc0

[assignUser]

I'd like to know why both commits I saw were different but maybe that'll just remain a mystery.

Yeah, probably ^^

[amoeba]

Thanks @assignUser. I ran the above and things look fine so I'm going to close this.

[kou]

I'd like to know why both commits I saw were different but maybe that'll just remain a mystery.

I think that some repositories in "git remote" of your local Git repository have apache-arrow-19.0.0-rc0 and apache-arrow-20.0.0-rc0. For example, my fork (kou/arrow) has apache-arrow-19.0.1-rc1 for testing: https://github.com/kou/arrow/tags

[amoeba]

Hrm, thanks @kou. Makes sense it could be something like that.