kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity
rails--rails/Gemfile.lock

312 lines
7.1 KiB
Text
Raw Normal View History

Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
GIT
remote: git://github.com/bkeepers/qu.git
revision: d098e2657c92e89a6413bebd9c033930759c061f
branch: master
specs:
qu (0.2.0)
qu-rails (0.2.0)
qu (= 0.2.0)
railties (>= 3.2, < 5)
qu-redis (0.2.0)
qu (= 0.2.0)
redis-namespace
Test against the mail gem's edge The edge version ships with a patch that uses composition over inheritance for the Mail::PartsList object (see mikel/mail#782). Let's test Action Mailer against it to prevent eventual regressions and experience it. Moreover, this branch makes the Action Mailer suite green against Rubinius.
2015-03-02 07:47:24 -05:00
GIT
remote: git://github.com/mikel/mail.git
revision: b159e0a542962fdd5e292a48cfffa560d7cf412e
specs:
mail (2.6.3.edge)
mime-types (>= 1.16, < 3)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
GIT
remote: git://github.com/rails/arel.git
revision: aac9da257f291ad8d2d4f914528881c240848bb2
branch: master
specs:
arel (7.0.0.alpha)
GIT
remote: git://github.com/rails/jquery-rails.git
revision: 272abdd319bb3381b23182b928b25320590096b0
branch: master
specs:
jquery-rails (4.0.3)
rails-dom-testing (~> 1.0)
railties (>= 4.2.0)
thor (>= 0.14, < 2.0)
Use latest sprockets-rails on internal dev
2015-04-26 11:42:13 -04:00
GIT
remote: git://github.com/rails/sprockets-rails.git
revision: 85b89c44ad40af3056899808475e6e4bf65c1f5a
branch: master
specs:
sprockets-rails (3.0.0.beta1)
actionpack (>= 4.0)
activesupport (>= 4.0)
sprockets (>= 3.0.0, < 4.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
PATH
remote: .
specs:
actionmailer (5.0.0.alpha)
actionpack (= 5.0.0.alpha)
actionview (= 5.0.0.alpha)
activejob (= 5.0.0.alpha)
mail (~> 2.5, >= 2.5.4)
rails-dom-testing (~> 1.0, >= 1.0.5)
actionpack (5.0.0.alpha)
actionview (= 5.0.0.alpha)
activesupport (= 5.0.0.alpha)
rack (~> 1.6)
Bump rack-test to fix nil values being sent to `parse_nested_query` I found that nil values were being incorrectly sent to `parse_nested_query` in Rack. Originally it was thought that Rails was doing something incorrect but it was actually rack-test. This was fixed in brynary/rack-test@4a4b2c1 and is no longer an issue. This commit bumps rack-test in Rails so changes to Rack don't cause failures. See rack/rack#813 for more information.
2015-03-01 16:52:17 -05:00
rack-test (~> 0.6.3)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
rails-dom-testing (~> 1.0, >= 1.0.5)
Let strip_tags leave HTML escaping to Rails. Prevents double escaping errors, such as "&amp;" becoming "&amp;amp;".
2015-03-07 12:48:06 -05:00
rails-html-sanitizer (~> 1.0, >= 1.0.2)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
actionview (5.0.0.alpha)
activesupport (= 5.0.0.alpha)
builder (~> 3.1)
erubis (~> 2.7.0)
rails-dom-testing (~> 1.0, >= 1.0.5)
Let strip_tags leave HTML escaping to Rails. Prevents double escaping errors, such as "&amp;" becoming "&amp;amp;".
2015-03-07 12:48:06 -05:00
rails-html-sanitizer (~> 1.0, >= 1.0.2)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
activejob (5.0.0.alpha)
activesupport (= 5.0.0.alpha)
globalid (>= 0.3.0)
activemodel (5.0.0.alpha)
activesupport (= 5.0.0.alpha)
builder (~> 3.1)
activerecord (5.0.0.alpha)
activemodel (= 5.0.0.alpha)
activesupport (= 5.0.0.alpha)
arel (= 7.0.0.alpha)
activesupport (5.0.0.alpha)
i18n (~> 0.7)
json (~> 1.7, >= 1.7.7)
minitest (~> 5.1)
thread_safe (~> 0.3, >= 0.3.4)
tzinfo (~> 1.1)
rails (5.0.0.alpha)
actionmailer (= 5.0.0.alpha)
actionpack (= 5.0.0.alpha)
actionview (= 5.0.0.alpha)
activejob (= 5.0.0.alpha)
activemodel (= 5.0.0.alpha)
activerecord (= 5.0.0.alpha)
activesupport (= 5.0.0.alpha)
bundler (>= 1.3.0, < 2.0)
railties (= 5.0.0.alpha)
sprockets-rails
railties (5.0.0.alpha)
actionpack (= 5.0.0.alpha)
activesupport (= 5.0.0.alpha)
method_source needs to be a hard dependency on railties
2015-03-05 09:58:17 -05:00
method_source
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
rake (>= 0.8.7)
thor (>= 0.18.1, < 2.0)
GEM
remote: https://rubygems.org/
specs:
amq-protocol (1.9.2)
backburner (0.4.6)
beaneater (~> 0.3.1)
dante (~> 0.1.5)
bcrypt (3.1.10)
Gemfile: temporay pin "bcrypt" version and run "bundle update bcrypt" on Linux Related: #19617, #19187, #19533, #19689, #19675. This is POC (Proof Of Concept) which bundler does not remove mingw lines. https://github.com/rails/rails/pull/19617#issuecomment-90293795
2015-04-06 19:35:02 -04:00
bcrypt (3.1.10-x64-mingw32)
bcrypt (3.1.10-x86-mingw32)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
beaneater (0.3.3)
benchmark-ips (2.1.1)
builder (3.2.2)
Unlock sneakers adapter version
2015-04-26 03:44:18 -04:00
bunny (1.7.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
amq-protocol (>= 1.9.2)
Uncomment byebug in framework Gemfile History: 1. `debugger` was there until d2ed433b where it was commented out, and I couldn't figure out why 2. Since then we inherited that when switching to `byebug` in 93559da4 Reasons: 1. It's nice to have a debugger when working on framework bugs 2. It's an uncommented dependency in app Gemfiles since Rails 4.2 (see fbe38c9e)
2015-04-24 01:24:50 -04:00
byebug (4.0.5)
columnize (= 0.9.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
celluloid (0.16.0)
timers (~> 4.0.0)
coffee-rails (4.1.0)
coffee-script (>= 2.2.0)
railties (>= 4.0.0, < 5.0)
coffee-script (2.3.0)
coffee-script-source
execjs
coffee-script-source (1.9.0)
Uncomment byebug in framework Gemfile History: 1. `debugger` was there until d2ed433b where it was commented out, and I couldn't figure out why 2. Since then we inherited that when switching to `byebug` in 93559da4 Reasons: 1. It's nice to have a debugger when working on framework bugs 2. It's an uncommented dependency in app Gemfiles since Rails 4.2 (see fbe38c9e)
2015-04-24 01:24:50 -04:00
columnize (0.9.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
connection_pool (2.1.1)
dalli (2.7.2)
dante (0.1.5)
delayed_job (4.0.6)
activesupport (>= 3.0, < 5.0)
Fixed ActiveJob integration tests
2015-03-05 16:41:14 -05:00
delayed_job_active_record (4.0.3)
activerecord (>= 3.0, < 5.0)
delayed_job (>= 3.0, < 4.1)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
erubis (2.7.0)
execjs (2.3.0)
globalid (0.3.3)
activesupport (>= 4.1.0)
hitimes (1.2.2)
Gemfile: temporay pin "bcrypt" version and run "bundle update bcrypt" on Linux Related: #19617, #19187, #19533, #19689, #19675. This is POC (Proof Of Concept) which bundler does not remove mingw lines. https://github.com/rails/rails/pull/19617#issuecomment-90293795
2015-04-06 19:35:02 -04:00
hitimes (1.2.2-x86-mingw32)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
i18n (0.7.0)
json (1.8.2)
kindlerb (0.1.1)
mustache
nokogiri
loofah (2.0.1)
nokogiri (>= 1.5.9)
metaclass (0.0.4)
Add method_source to gemfile
2015-01-23 20:34:43 -05:00
method_source (0.8.2)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
mime-types (2.4.3)
mini_portile (0.6.2)
minitest (5.3.3)
mocha (0.14.0)
metaclass (~> 0.0.1)
mono_logger (1.1.0)
Test using sprockets 3
2015-03-29 20:56:00 -04:00
multi_json (1.11.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
mustache (1.0.0)
mysql (2.9.1)
mysql2 (0.3.18)
nokogiri (1.6.6.2)
mini_portile (~> 0.6.0)
Gemfile: temporay pin "bcrypt" version and run "bundle update bcrypt" on Linux Related: #19617, #19187, #19533, #19689, #19675. This is POC (Proof Of Concept) which bundler does not remove mingw lines. https://github.com/rails/rails/pull/19617#issuecomment-90293795
2015-04-06 19:35:02 -04:00
nokogiri (1.6.6.2-x64-mingw32)
mini_portile (~> 0.6.0)
nokogiri (1.6.6.2-x86-mingw32)
mini_portile (~> 0.6.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
pg (0.18.1)
psych (2.0.13)
que (0.9.2)
queue_classic (3.1.0)
pg (>= 0.17, < 0.19)
racc (1.4.12)
rack (1.6.0)
rack-cache (1.2)
rack (>= 0.4)
rack-protection (1.5.3)
rack
rack-test (0.6.3)
rack (>= 1.0)
rails-deprecated_sanitizer (1.0.3)
activesupport (>= 4.2.0.alpha)
Use latest sprockets-rails on internal dev
2015-04-26 11:42:13 -04:00
rails-dom-testing (1.0.6)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
activesupport (>= 4.2.0.beta, < 5.0)
nokogiri (~> 1.6.0)
rails-deprecated_sanitizer (>= 1.0.1)
Use the released gem
2015-03-10 16:31:35 -04:00
rails-html-sanitizer (1.0.2)
loofah (~> 2.0)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
rake (10.4.2)
rdoc (4.2.0)
redcarpet 3.2.2 has an XSS vulnerability see: http://www.openwall.com/lists/oss-security/2015/04/07/11
2015-04-09 05:20:53 -04:00
redcarpet (3.2.3)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
redis (3.2.1)
redis-namespace (1.5.1)
redis (~> 3.0, >= 3.0.4)
resque (1.25.2)
mono_logger (~> 1.0)
multi_json (~> 1.0)
redis-namespace (~> 1.3)
sinatra (>= 0.9.2)
vegas (~> 0.1.2)
resque-scheduler (4.0.0)
mono_logger (~> 1.0)
redis (~> 3.0)
resque (~> 1.25)
rufus-scheduler (~> 3.0)
rufus-scheduler (3.0.9)
tzinfo
sdoc (0.4.1)
json (~> 1.7, >= 1.7.7)
rdoc (~> 4.0)
sequel (4.19.0)
serverengine (1.5.10)
sigdump (~> 0.2.2)
sidekiq (3.3.2)
celluloid (>= 0.16.0)
connection_pool (>= 2.1.1)
json
redis (>= 3.0.6)
redis-namespace (>= 1.3.1)
sigdump (0.2.2)
sinatra (1.4.5)
rack (~> 1.4)
rack-protection (~> 1.4)
tilt (~> 1.3, >= 1.3.4)
Unlock sneakers adapter version
2015-04-26 03:44:18 -04:00
sneakers (1.0.4)
bunny (~> 1.7.0)
serverengine (~> 1.5.5)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
thor
Unlock sneakers adapter version
2015-04-26 03:44:18 -04:00
thread (~> 0.1.7)
Use latest sprockets-rails on internal dev
2015-04-26 11:42:13 -04:00
sprockets (3.0.2)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
rack (~> 1.0)
sqlite3 (1.3.10)
stackprof (0.2.7)
sucker_punch (1.3.2)
celluloid (~> 0.16.0)
thor (0.19.1)
Unlock sneakers adapter version
2015-04-26 03:44:18 -04:00
thread (0.1.7)
Use latest sprockets-rails on internal dev
2015-04-26 11:42:13 -04:00
thread_safe (0.3.5)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
tilt (1.4.1)
timers (4.0.1)
hitimes
turbolinks (2.5.3)
coffee-rails
tzinfo (1.2.2)
thread_safe (~> 0.1)
uglifier (2.7.0)
execjs (>= 0.3.0)
json (>= 1.8.0)
vegas (0.1.11)
rack (>= 1.0.0)
w3c_validators (1.2)
json
nokogiri
PLATFORMS
ruby
Gemfile: temporay pin "bcrypt" version and run "bundle update bcrypt" on Linux Related: #19617, #19187, #19533, #19689, #19675. This is POC (Proof Of Concept) which bundler does not remove mingw lines. https://github.com/rails/rails/pull/19617#issuecomment-90293795
2015-04-06 19:35:02 -04:00
x64-mingw32
x86-mingw32
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
DEPENDENCIES
activerecord-jdbcmysql-adapter (>= 1.3.0)
activerecord-jdbcpostgresql-adapter (>= 1.3.0)
activerecord-jdbcsqlite3-adapter (>= 1.3.0)
arel!
backburner
Gemfile: temporay pin "bcrypt" version and run "bundle update bcrypt" on Linux Related: #19617, #19187, #19533, #19689, #19675. This is POC (Proof Of Concept) which bundler does not remove mingw lines. https://github.com/rails/rails/pull/19617#issuecomment-90293795
2015-04-06 19:35:02 -04:00
bcrypt (~> 3.1.10)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
benchmark-ips
Uncomment byebug in framework Gemfile History: 1. `debugger` was there until d2ed433b where it was commented out, and I couldn't figure out why 2. Since then we inherited that when switching to `byebug` in 93559da4 Reasons: 1. It's nice to have a debugger when working on framework bugs 2. It's an uncommented dependency in app Gemfiles since Rails 4.2 (see fbe38c9e)
2015-04-24 01:24:50 -04:00
byebug
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
coffee-rails (~> 4.1.0)
dalli (>= 2.2.1)
delayed_job
Fixed ActiveJob integration tests
2015-03-05 16:41:14 -05:00
delayed_job_active_record
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
jquery-rails!
json
kindlerb (= 0.1.1)
Test against the mail gem's edge The edge version ships with a patch that uses composition over inheritance for the Mail::PartsList object (see mikel/mail#782). Let's test Action Mailer against it to prevent eventual regressions and experience it. Moreover, this branch makes the Action Mailer suite green against Rubinius.
2015-03-02 07:47:24 -05:00
mail!
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
minitest (< 5.3.4)
mocha (~> 0.14)
mysql (>= 2.9.0)
Format the time string according to the precision of the time column It is also necessary to format a time column like a datetime column.
2015-02-12 13:04:47 -05:00
mysql2 (>= 0.3.18)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
nokogiri (>= 1.4.5)
pg (>= 0.18.0)
psych (~> 2.0)
qu-rails!
qu-redis
que
queue_classic
racc (>= 1.4.6)
rack-cache (~> 1.2)
rails!
rake (>= 10.3)
redcarpet 3.2.2 has an XSS vulnerability see: http://www.openwall.com/lists/oss-security/2015/04/07/11
2015-04-09 05:20:53 -04:00
redcarpet (~> 3.2.3)
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
resque
resque-scheduler
sdoc (~> 0.4.0)
sequel
sidekiq
Unlock sneakers adapter version
2015-04-26 03:44:18 -04:00
sneakers
Test using sprockets 3
2015-03-29 20:56:00 -04:00
sprockets (~> 3.0.0.rc.1)
Use latest sprockets-rails on internal dev
2015-04-26 11:42:13 -04:00
sprockets-rails!
Track Gemfile.lock at the repository The main reason is to make bisect easier. In some points, we have a lot of git dependencies. Since we don't have the information of which commit we are referring to, bundler get the latest commit of the master branch of the dependency. This sometimes returns a version that is not compatible with Rails anymore, making the tests fail and the harder to identify the commit that introduced a bug. Also this will make sure that a contributor will always get a set of dependencies that are passing with our tests. In our CI server we delete the lock file to make sure we are always testing against the newest release of our dependencies.
2015-02-18 11:30:25 -05:00
sqlite3 (~> 1.3.6)
stackprof
sucker_punch
turbolinks
uglifier (>= 1.3.0)
w3c_validators
Generate Bundler 1.10.1 lockfile
2015-05-29 01:40:29 -04:00
BUNDLED WITH
Ensure symbols passed to `select` are always quoted Our general contract in Active Record is that strings are assumed to be SQL literals, and symbols are assumed to reference a column. If a from clause is given, we shouldn't include the table name, but we should still quote the value as if it were a column. Upon fixing this, the tests were still failing on SQLite. This was because the column name being returned by the query was `"\"join\""` instead of `"join"`. This is actually a bug in SQLite that was fixed a long time ago, but I was using the version of SQLite included by OS X which has this bug. Since I'm guessing this will be a common case for contributors, I also added an explicit check with a more helpful error message. Fixes #20360
2015-05-30 14:26:41 -04:00
1.10.2
Copy permalink