-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify pre-release string to development version #81
Comments
I'm OK with adding a suffix but it seems that it's a Bundler bug. https://github.com/tdiary/tdiary-core/actions/runs/7470853111/job/20330178338#step:6:15
"that source" means "rubygems repository https://rubygems.org/ or installed locally" not "rubygems repository https://rubygems.org/", right? |
I'm not sure what you mean. https://github.com/tdiary/tdiary-core/actions/runs/7470853111/job/20330178338#step:6:15 is not master/head version. Ruby 3.0 or other stable version don't have Bundler will not pick prerelease version in default. If stringio or other default gems is marked with prelease flag like |
Just noting that I was trying to update JRuby's copy of gems from CRuby master and ran into this for both stringio and strscan (3.1.1 referenced there but not released). I see other gems that are |
I'm also running into this now. Seeing the following message when deploying:
It looks like running For reference, our only gem that depends on this is
I'm not sure where it's finding 3.1.1 and trying to use that. I will adjust manually for now but anything we can do to solve this longer-term? Thanks, Joshua |
Rails CI agaist Ruby master branch is getting the same Refer to https://buildkite.com/rails/rails-nightly/builds/971#0191aa3d-c398-4c46-a32b-69de837da9e7/1259 For similar LoadErrors, we have applied workaround by updating Gemfile.lock explicitly for stringio 3.1.1, strscan 3.0.4, strscan 3.0.2 and psych 5.1.1.1 like rails/rails#52123 . However, this workaround does not work for stringio 3.1.2.dev . As far as I understand the original issue can be resolved once rubygems/rubygems#5535 or rubygems/rubygems#5535 is merged to RubyGems. Steps to reproduce
Expected behaviorIt should pass as it runs against Ruby 3.3.4.
Actual behaviorIt raises the following
|
Perhaps you meant rubygems/rubygems#5529 or rubygems/rubygems#5535 ? |
My bad.
Right. |
Hmm. I'm not sure your workflow. Is the following correct?
|
Are you using master Ruby? |
The Rails case shows that ".dev" approach causes another problem, right? |
Yes. In my understanding, Rails case happened with |
OK. If you use master Ruby for |
Opened rubygems/rubygems#7996 because it looks like a bundler issue. |
I understand to use development version policy like "stringio-3.1.1". But this policy is harmful for library developer who used master version of Ruby.
I ususally use master version that is
ruby-dev
definition of ruby-build and develop software. When I didbundle update
ontdiary/tdiary-core
, it seems working fine. Butstringio-3.1.1
is not released on rubygems.org. So, we get preparation failure on GitHub Actions like:https://github.com/tdiary/tdiary-core/actions/runs/7470853111/job/20330178338
Can you add
.dev
suffix to development version?.dev
is example, I'm okay to any string that is prelease flag. After that, I easily find dev version of dependencies.The text was updated successfully, but these errors were encountered: