summaryrefslogtreecommitdiff
path: root/spec/support/artifice/vcr_cassettes/realworld/index.rubygems.org/info/eventmachine
diff options
context:
space:
mode:
authorBundlerbot <bot@bundler.io>2019-08-27 22:46:39 +0000
committerBundlerbot <bot@bundler.io>2019-08-27 22:46:39 +0000
commitc8081842e4e0a4f553831a5d688fb537f9481dd0 (patch)
tree889e4e88b609af7fcf98aa9bf6841ba95e239d68 /spec/support/artifice/vcr_cassettes/realworld/index.rubygems.org/info/eventmachine
parent3db1ace2f59e3db5a7e1d641b646874bcee80c9d (diff)
parent99df87b7b05fc6b88eead741b6141828c912db7e (diff)
downloadbundler-c8081842e4e0a4f553831a5d688fb537f9481dd0.tar.gz
Merge #7332
7332: Fix version number in release playbook r=deivid-rodriguez a=deivid-rodriguez ### What was the end-user problem that led to this PR? The problem was that I'm about to release bundler, but I'm unsure which one is the right version number. ### What was your diagnosis of the problem? My diagnosis was that the release playbook is probably wrong, because looking at https://rubygems.org/gems/bundler/versions, we don't really ship `.pre.0`. versions. ### What is your fix for the problem, implemented in this PR? My fix is to document `.pre.1` as the first prerelease on a minor series, since that's what we usually do. Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
Diffstat (limited to 'spec/support/artifice/vcr_cassettes/realworld/index.rubygems.org/info/eventmachine')
0 files changed, 0 insertions, 0 deletions