Open luke-hill opened 11 months ago
I suspect this check https://github.com/cucumber/polyglot-release/blob/51c37ccf5912c38f952ede8ba4b2bb6447f22757/polyglot-release#L287-L290 also matched the 3.0.0-rc1 tag.
No. It does not.
mpkorstanje@nyx:~/Projects/cucumber/cucumber-jvm$ git tag --list | head
v1.0.0
v1.0.0-RC3
v1.0.0.RC1
v1.0.0.RC10
v1.0.0.RC11
v1.0.0.RC12
v1.0.0.RC13
v1.0.0.RC14
v1.0.0.RC15
v1.0.0.RC16
mpkorstanje@nyx:~/Projects/cucumber/cucumber-jvm$ git tag --list v1.0.0
v1.0.0
@luke-hill could you check this with your git version?
Otherwise the only alternative I can think of is that you already had a 3.0.0 tag locally. And that you've deleted it when creating the latest release manually.
That didn't show that tag.
But I did the manual release like you showed me before. Making the changelog commit and version commit by hand, then pushing to main then making a new branch and pushing to that one.
👓 What did you see?
✅ What did you expect to see?
polyglot-release working for cucumber-rails (3.0.0.rc1 is released)
📦 Which tool/library version are you using?
polyglot-release latest
🔬 How could we reproduce it?
Try run polyglot-release
Steps to reproduce the behavior:
📚 Any additional context?
This text was originally generated from a template, then edited by hand. You can modify the template here.