豆豆友情提示:这是一个非官方 GitHub 代理镜像,主要用于网络测试或访问加速。请勿在此进行登录、注册或处理任何敏感信息。进行这些操作请务必访问官方网站 github.com。 Raw 内容也通过此代理提供。
Skip to content

More descriptive error message for tag <tag> does not exist#12984

Merged
Nishnha merged 3 commits intomainfrom
nishnha/more-helpful-error
Aug 29, 2025
Merged

More descriptive error message for tag <tag> does not exist#12984
Nishnha merged 3 commits intomainfrom
nishnha/more-helpful-error

Conversation

@Nishnha
Copy link
Copy Markdown
Member

@Nishnha Nishnha commented Aug 29, 2025

What are you trying to accomplish?

Add a more helpful error message to the tag <tag> does not exist error we sometimes see when releasing Gems

Anything you want to highlight for special attention from reviewers?

Tried to add it somewhere helpful

How will you know you've accomplished your goal?

We know what to do next time we run into this error

Checklist

N/A

@Nishnha Nishnha requested a review from a team as a code owner August 29, 2025 23:24
honeyankit
honeyankit previously approved these changes Aug 29, 2025
honeyankit
honeyankit previously approved these changes Aug 29, 2025
@Nishnha Nishnha enabled auto-merge (squash) August 29, 2025 23:28
@Nishnha Nishnha merged commit d0a006d into main Aug 29, 2025
73 checks passed
@Nishnha Nishnha deleted the nishnha/more-helpful-error branch August 29, 2025 23:46
@jeffwidman
Copy link
Copy Markdown
Member

I think this wording actually introduces some confusion... we shouldn't actually need to restart from the bump-versions bit, we should be okay to simply retrigger a new run of release-to-rubygems workflow, provided it happens on a new runner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants