mirrors
/
rails
mirror of https://github.com/rails/rails
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
rails/Gemfile.lock

348 lines
8.2 KiB
Plaintext
Raw Normal View History

implement `provider_job_id` for `queue_classic`. The latest, currently unreleased, version of queue_classic is required for this to work. See https://github.com/QueueClassic/queue_classic/pull/262 for more details.
2015-08-13 15:56:06 +08:00
GIT
remote: git://github.com/QueueClassic/queue_classic.git
revision: d144db29f1436e9e8b3c7a1a1ecd4442316a9ecd
Add master branch to github gems to be able to use local clones
2015-09-01 19:44:32 +08:00
branch: master
implement `provider_job_id` for `queue_classic`. The latest, currently unreleased, version of queue_classic is required for this to work. See https://github.com/QueueClassic/queue_classic/pull/262 for more details.
2015-08-13 15:56:06 +08:00
specs:
queue_classic (3.2.0.alpha)
pg (>= 0.17, < 0.19)
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-19 00:30:25 +08: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
run against edge sass to eliminate circular require warnings
2015-09-30 22:42:31 +08:00
GIT
remote: git://github.com/sass/sass.git
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
revision: bce9509f396225d721501ea1070a6871b708abb1
run against edge sass to eliminate circular require warnings
2015-09-30 22:42:31 +08:00
branch: stable
specs:
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
sass (3.4.20)
run against edge sass to eliminate circular require warnings
2015-09-30 22:42:31 +08:00
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-19 00:30:25 +08:00
PATH
remote: .
specs:
Change `alpha` to `beta1` to prep for release of Rails 5 :tada: :beers:
2015-12-19 01:07:10 +08:00
actioncable (5.0.0.beta1)
actionpack (= 5.0.0.beta1)
Revert "Move async execution from celluloid to concurrent-ruby"
2016-01-09 03:09:25 +08:00
celluloid (~> 0.17.2)
Initial stab at adding Action Cable to rails/master
2015-12-14 23:38:37 +08:00
coffee-rails (~> 4.1.0)
em-hiredis (~> 0.3.0)
faye-websocket (~> 0.10.0)
redis (~> 3.0)
websocket-driver (~> 0.6.1)
Change `alpha` to `beta1` to prep for release of Rails 5 :tada: :beers:
2015-12-19 01:07:10 +08:00
actionmailer (5.0.0.beta1)
actionpack (= 5.0.0.beta1)
actionview (= 5.0.0.beta1)
activejob (= 5.0.0.beta1)
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-19 00:30:25 +08:00
mail (~> 2.5, >= 2.5.4)
rails-dom-testing (~> 1.0, >= 1.0.5)
Change `alpha` to `beta1` to prep for release of Rails 5 :tada: :beers:
2015-12-19 01:07:10 +08:00
actionpack (5.0.0.beta1)
actionview (= 5.0.0.beta1)
activesupport (= 5.0.0.beta1)
point at rack master
2015-08-21 04:43:57 +08:00
rack (~> 2.x)
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-02 05:52:17 +08: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-19 00:30:25 +08: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-08 01:48:06 +08:00
rails-html-sanitizer (~> 1.0, >= 1.0.2)
Change `alpha` to `beta1` to prep for release of Rails 5 :tada: :beers:
2015-12-19 01:07:10 +08:00
actionview (5.0.0.beta1)
activesupport (= 5.0.0.beta1)
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-19 00:30:25 +08:00
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-08 01:48:06 +08:00
rails-html-sanitizer (~> 1.0, >= 1.0.2)
Change `alpha` to `beta1` to prep for release of Rails 5 :tada: :beers:
2015-12-19 01:07:10 +08:00
activejob (5.0.0.beta1)
activesupport (= 5.0.0.beta1)
Use released GlobalID now that it provides URI::GID::MissingModelIdError for Active Job
2015-12-18 08:20:19 +08:00
globalid (>= 0.3.6)
Change `alpha` to `beta1` to prep for release of Rails 5 :tada: :beers:
2015-12-19 01:07:10 +08:00
activemodel (5.0.0.beta1)
activesupport (= 5.0.0.beta1)
activerecord (5.0.0.beta1)
activemodel (= 5.0.0.beta1)
activesupport (= 5.0.0.beta1)
Use released arel
2015-12-18 04:11:29 +08:00
arel (~> 7.0)
Change `alpha` to `beta1` to prep for release of Rails 5 :tada: :beers:
2015-12-19 01:07:10 +08:00
activesupport (5.0.0.beta1)
Using released concurrent-ruby
2015-11-17 04:26:39 +08:00
concurrent-ruby (~> 1.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-19 00:30:25 +08:00
i18n (~> 0.7)
json (~> 1.7, >= 1.7.7)
Add method_source dependency to activesupport
2015-06-21 03:00:35 +08: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-19 00:30:25 +08:00
minitest (~> 5.1)
tzinfo (~> 1.1)
Change `alpha` to `beta1` to prep for release of Rails 5 :tada: :beers:
2015-12-19 01:07:10 +08:00
rails (5.0.0.beta1)
actioncable (= 5.0.0.beta1)
actionmailer (= 5.0.0.beta1)
actionpack (= 5.0.0.beta1)
actionview (= 5.0.0.beta1)
activejob (= 5.0.0.beta1)
activemodel (= 5.0.0.beta1)
activerecord (= 5.0.0.beta1)
activesupport (= 5.0.0.beta1)
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-19 00:30:25 +08:00
bundler (>= 1.3.0, < 2.0)
Change `alpha` to `beta1` to prep for release of Rails 5 :tada: :beers:
2015-12-19 01:07:10 +08:00
railties (= 5.0.0.beta1)
Require sprockets-rails >= 2 Fixes https://github.com/rails/rails/commit/4d157ea8c15186c4903fa83f2dc51a5f78d13a37 Without any specification about the version of sprockets-rails, running a `bundle install` on a brand new app might result in sprockets 0.0.1 being installed. However, the minimum requirement is sprockets-rails 2 (see https://github.com/rails/rails/pull/17752/files)
2015-09-02 00:29:16 +08:00
sprockets-rails (>= 2.0.0)
Change `alpha` to `beta1` to prep for release of Rails 5 :tada: :beers:
2015-12-19 01:07:10 +08:00
railties (5.0.0.beta1)
actionpack (= 5.0.0.beta1)
activesupport (= 5.0.0.beta1)
method_source needs to be a hard dependency on railties
2015-03-05 22:58:17 +08: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-19 00:30:25 +08:00
rake (>= 0.8.7)
thor (>= 0.18.1, < 2.0)
GEM
remote: https://rubygems.org/
specs:
point at rack master
2015-08-21 04:43:57 +08:00
amq-protocol (2.0.0)
Use released arel
2015-12-18 04:11:29 +08:00
arel (7.0.0)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
backburner (1.2.0)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
beaneater (~> 1.0)
dante (> 0.1.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-19 00:30:25 +08:00
bcrypt (3.1.10)
Avoid conditionals in the Gemfile "conditionals in the gemfile creates conditional code in the Gemfile.lock. Since it is checked in the repository I think it is better to avoid it"
2015-12-17 01:33:09 +08:00
bcrypt-ruby (3.0.1)
bcrypt-ruby (3.0.1-x86-mingw32)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
beaneater (1.0.0)
benchmark-ips (2.3.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-19 00:30:25 +08:00
builder (3.2.2)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
bunny (2.2.1)
Ruby 2.2.3 in windows need nokogiri 1.6.7.rc3 as it's the only version having correct pre-compiled so
2015-09-12 22:04:31 +08:00
amq-protocol (>= 2.0.0)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
byebug (8.2.1)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
celluloid (0.17.2)
celluloid-essentials
celluloid-extras
celluloid-fsm
celluloid-pool
celluloid-supervision
timers (>= 4.1.1)
celluloid-essentials (0.20.5)
timers (>= 4.1.1)
celluloid-extras (0.20.5)
timers (>= 4.1.1)
celluloid-fsm (0.20.5)
timers (>= 4.1.1)
celluloid-pool (0.20.5)
timers (>= 4.1.1)
celluloid-supervision (0.20.5)
timers (>= 4.1.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-19 00:30:25 +08:00
coffee-rails (4.1.0)
coffee-script (>= 2.2.0)
railties (>= 4.0.0, < 5.0)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
coffee-script (2.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-19 00:30:25 +08:00
coffee-script-source
execjs
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
coffee-script-source (1.10.0)
Using released concurrent-ruby
2015-11-17 04:26:39 +08:00
concurrent-ruby (1.0.0)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
connection_pool (2.2.0)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
dalli (2.7.5)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
dante (0.2.0)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
delayed_job (4.1.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-19 00:30:25 +08:00
activesupport (>= 3.0, < 5.0)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
delayed_job_active_record (4.1.0)
activerecord (>= 3.0, < 5)
delayed_job (>= 3.0, < 5)
Initial stab at adding Action Cable to rails/master
2015-12-14 23:38:37 +08:00
em-hiredis (0.3.0)
eventmachine (~> 1.0)
hiredis (~> 0.5.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-19 00:30:25 +08:00
erubis (2.7.0)
Initial stab at adding Action Cable to rails/master
2015-12-14 23:38:37 +08:00
eventmachine (1.0.8)
point at rack master
2015-08-21 04:43:57 +08:00
execjs (2.6.0)
Initial stab at adding Action Cable to rails/master
2015-12-14 23:38:37 +08:00
faye-websocket (0.10.2)
eventmachine (>= 0.12.0)
websocket-driver (>= 0.5.1)
implements an evented file update checker [Puneet Agarwal] This is the implementation of the file update checker written by Puneet Agarwal for GSoC 2015 (except for the tiny version of the listen gem, which was 3.0.2 in the original patch). Puneet's branch became too out of sync with upstream. This is the final work in one single clean commit. Credit goes in the first line using a convention understood by the contrib app.
2015-10-13 02:41:14 +08:00
ffi (1.9.10)
ffi (1.9.10-x64-mingw32)
ffi (1.9.10-x86-mingw32)
Use released GlobalID now that it provides URI::GID::MissingModelIdError for Active Job
2015-12-18 08:20:19 +08:00
globalid (0.3.6)
activesupport (>= 4.1.0)
Initial stab at adding Action Cable to rails/master
2015-12-14 23:38:37 +08:00
hiredis (0.5.2)
Do not use conditionals at Gemfile This will make the Gemfile.lock be dirty in some environments
2015-09-15 07:12:09 +08:00
hitimes (1.2.3)
hitimes (1.2.3-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-19 00:30:25 +08:00
i18n (0.7.0)
Install jquery-rails It will make sure that the generated application in the tests get the gem.
2015-12-18 14:12:50 +08:00
jquery-rails (4.0.5)
rails-dom-testing (~> 1.0)
railties (>= 4.2.0)
thor (>= 0.14, < 2.0)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
json (1.8.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-19 00:30:25 +08:00
kindlerb (0.1.1)
mustache
nokogiri
Upgrade to listen 3.0.5, re-enable tests In listen 3.0.4 and below, the `#stop` method on the notification backends are a no-op, meaning that we are leaking them per test. This ended up triggering another bug in Ruby that causes our builds to fail randomly on CI. listen bug: https://github.com/guard/listen/issues/353 ruby bug: https://bugs.ruby-lang.org/issues/11744
2015-11-27 02:31:52 +08:00
listen (3.0.5)
implements an evented file update checker [Puneet Agarwal] This is the implementation of the file update checker written by Puneet Agarwal for GSoC 2015 (except for the tiny version of the listen gem, which was 3.0.2 in the original patch). Puneet's branch became too out of sync with upstream. This is the final work in one single clean commit. Credit goes in the first line using a convention understood by the contrib app.
2015-10-13 02:41:14 +08:00
rb-fsevent (>= 0.9.3)
rb-inotify (>= 0.9)
point at rack master
2015-08-21 04:43:57 +08:00
loofah (2.0.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-19 00:30:25 +08:00
nokogiri (>= 1.5.9)
Use released mail gem
2015-12-18 03:16:08 +08:00
mail (2.6.3)
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-19 00:30:25 +08:00
metaclass (0.0.4)
Add method_source to gemfile
2015-01-24 09:34:43 +08:00
method_source (0.8.2)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
mime-types (2.99)
Update nokogiri to 1.6.7 This picks up https://github.com/sparklemotion/nokogiri/pull/1218 which allows nokogiri to compile on Xcode-only OS X systems.
2015-12-11 00:25:25 +08:00
mini_portile2 (2.0.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-19 00:30:25 +08:00
minitest (5.3.3)
mocha (0.14.0)
metaclass (~> 0.0.1)
mono_logger (1.1.0)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
multi_json (1.11.2)
mustache (1.0.2)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
mysql2 (0.4.2)
Avoid conditionals in the Gemfile "conditionals in the gemfile creates conditional code in the Gemfile.lock. Since it is checked in the repository I think it is better to avoid it"
2015-12-17 01:33:09 +08:00
mysql2 (0.4.2-x64-mingw32)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
mysql2 (0.4.2-x86-mingw32)
Use release sprockets-rails
2015-12-18 04:22:58 +08:00
nokogiri (1.6.7.1)
Update nokogiri to 1.6.7 This picks up https://github.com/sparklemotion/nokogiri/pull/1218 which allows nokogiri to compile on Xcode-only OS X systems.
2015-12-11 00:25:25 +08:00
mini_portile2 (~> 2.0.0.rc2)
Use release sprockets-rails
2015-12-18 04:22:58 +08:00
nokogiri (1.6.7.1-x64-mingw32)
Avoid conditionals in the Gemfile "conditionals in the gemfile creates conditional code in the Gemfile.lock. Since it is checked in the repository I think it is better to avoid it"
2015-12-17 01:33:09 +08:00
mini_portile2 (~> 2.0.0.rc2)
Use release sprockets-rails
2015-12-18 04:22:58 +08:00
nokogiri (1.6.7.1-x86-mingw32)
Avoid conditionals in the Gemfile "conditionals in the gemfile creates conditional code in the Gemfile.lock. Since it is checked in the repository I think it is better to avoid it"
2015-12-17 01:33:09 +08:00
mini_portile2 (~> 2.0.0.rc2)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
pg (0.18.4)
pg (0.18.4-x64-mingw32)
pg (0.18.4-x86-mingw32)
psych (2.0.16)
Initial stab at adding Action Cable to rails/master
2015-12-14 23:38:37 +08:00
puma (2.15.3)
Ruby 2.2.3 in windows need nokogiri 1.6.7.rc3 as it's the only version having correct pre-compiled so
2015-09-12 22:04:31 +08:00
que (0.11.2)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
racc (1.4.14)
Use released rack
2015-12-18 14:53:38 +08:00
rack (2.0.0.alpha)
json
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
rack-cache (1.5.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-19 00:30:25 +08:00
rack (>= 0.4)
rack-test (0.6.3)
rack (>= 1.0)
rails-deprecated_sanitizer (1.0.3)
activesupport (>= 4.2.0.alpha)
point at rack master
2015-08-21 04:43:57 +08:00
rails-dom-testing (1.0.7)
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-19 00:30:25 +08:00
activesupport (>= 4.2.0.beta, < 5.0)
nokogiri (~> 1.6.0)
rails-deprecated_sanitizer (>= 1.0.1)
Use the released gem
2015-03-11 04:31:35 +08: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-19 00:30:25 +08:00
rake (10.4.2)
implements an evented file update checker [Puneet Agarwal] This is the implementation of the file update checker written by Puneet Agarwal for GSoC 2015 (except for the tiny version of the listen gem, which was 3.0.2 in the original patch). Puneet's branch became too out of sync with upstream. This is the final work in one single clean commit. Credit goes in the first line using a convention understood by the contrib app.
2015-10-13 02:41:14 +08:00
rb-fsevent (0.9.6)
rb-inotify (0.9.5)
ffi (>= 0.5.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-19 00:30:25 +08:00
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 17:20:53 +08:00
redcarpet (3.2.3)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
redis (3.2.2)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
redis-namespace (1.5.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-19 00:30:25 +08:00
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)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
rufus-scheduler (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-19 00:30:25 +08:00
sdoc (0.4.1)
json (~> 1.7, >= 1.7.7)
rdoc (~> 4.0)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
sequel (4.29.0)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
serverengine (1.5.11)
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-19 00:30:25 +08:00
sigdump (~> 0.2.2)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
sidekiq (4.0.1)
concurrent-ruby (~> 1.0)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
connection_pool (~> 2.2, >= 2.2.0)
json (~> 1.0)
redis (~> 3.2, >= 3.2.1)
sigdump (0.2.3)
point at rack master
2015-08-21 04:43:57 +08:00
sinatra (1.0)
rack (>= 1.0)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
sneakers (2.3.5)
Ruby 2.2.3 in windows need nokogiri 1.6.7.rc3 as it's the only version having correct pre-compiled so
2015-09-12 22:04:31 +08:00
bunny (~> 2.2.0)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
serverengine (~> 1.5.11)
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-19 00:30:25 +08:00
thor
Unlock sneakers adapter version
2015-04-26 15:44:18 +08:00
thread (~> 0.1.7)
Use sprockets 3 in the Rails 5 release
2015-12-17 02:30:58 +08:00
sprockets (3.5.2)
concurrent-ruby (~> 1.0)
rack (> 1, < 3)
Use release sprockets-rails
2015-12-18 04:22:58 +08:00
sprockets-rails (3.0.0)
actionpack (>= 4.0)
activesupport (>= 4.0)
sprockets (>= 3.0.0)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
sqlite3 (1.3.11)
Avoid conditionals in the Gemfile "conditionals in the gemfile creates conditional code in the Gemfile.lock. Since it is checked in the repository I think it is better to avoid it"
2015-12-17 01:33:09 +08:00
sqlite3 (1.3.11-x64-mingw32)
sqlite3 (1.3.11-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-19 00:30:25 +08:00
stackprof (0.2.7)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
sucker_punch (1.6.0)
celluloid (~> 0.17.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-19 00:30:25 +08:00
thor (0.19.1)
Unlock sneakers adapter version
2015-04-26 15:44:18 +08:00
thread (0.1.7)
Use latest sprockets-rails on internal dev
2015-04-26 23:42:13 +08:00
thread_safe (0.3.5)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
timers (4.1.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-19 00:30:25 +08:00
hitimes
Use released turbolinks in the test suite
2015-12-17 22:37:03 +08:00
turbolinks (2.5.3)
coffee-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-19 00:30:25 +08:00
tzinfo (1.2.2)
thread_safe (~> 0.1)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
tzinfo-data (1.2015.7)
Ruby 2.2.3 in windows need nokogiri 1.6.7.rc3 as it's the only version having correct pre-compiled so
2015-09-12 22:04:31 +08:00
tzinfo (>= 1.0.0)
uglifier (2.7.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-19 00:30:25 +08:00
execjs (>= 0.3.0)
json (>= 1.8.0)
vegas (0.1.11)
rack (>= 1.0.0)
w3c_validators (1.2)
json
nokogiri
Initial stab at adding Action Cable to rails/master
2015-12-14 23:38:37 +08:00
websocket-driver (0.6.3)
websocket-extensions (>= 0.1.0)
websocket-extensions (0.1.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-19 00:30:25 +08:00
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-07 07:35:02 +08: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-19 00:30:25 +08:00
DEPENDENCIES
activerecord-jdbcmysql-adapter (>= 1.3.0)
activerecord-jdbcpostgresql-adapter (>= 1.3.0)
activerecord-jdbcsqlite3-adapter (>= 1.3.0)
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-07 07:35:02 +08:00
bcrypt (~> 3.1.10)
Avoid conditionals in the Gemfile "conditionals in the gemfile creates conditional code in the Gemfile.lock. Since it is checked in the repository I think it is better to avoid it"
2015-12-17 01:33:09 +08:00
bcrypt-ruby (~> 3.0.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-19 00:30:25 +08: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 13:24:50 +08: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-19 00:30:25 +08:00
coffee-rails (~> 4.1.0)
dalli (>= 2.2.1)
delayed_job
Fixed ActiveJob integration tests
2015-03-06 05:41:14 +08:00
delayed_job_active_record
Install jquery-rails It will make sure that the generated application in the tests get the gem.
2015-12-18 14:12:50 +08:00
jquery-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-19 00:30:25 +08:00
json
kindlerb (= 0.1.1)
Upgrade to listen 3.0.5, re-enable tests In listen 3.0.4 and below, the `#stop` method on the notification backends are a no-op, meaning that we are leaking them per test. This ended up triggering another bug in Ruby that causes our builds to fail randomly on CI. listen bug: https://github.com/guard/listen/issues/353 ruby bug: https://bugs.ruby-lang.org/issues/11744
2015-11-27 02:31:52 +08:00
listen (~> 3.0.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-19 00:30:25 +08:00
minitest (< 5.3.4)
mocha (~> 0.14)
Revert "Add prepared statements support for `Mysql2Adapter`"
2015-11-27 02:53:10 +08:00
mysql2 (>= 0.4.0)
Require Nokogiri >= 1.6.7.1 Many CVEs released: https://groups.google.com/forum/#!topic/ruby-security-ann/aSbgDiwb24s
2015-12-18 06:35:25 +08:00
nokogiri (>= 1.6.7.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-19 00:30:25 +08:00
pg (>= 0.18.0)
psych (~> 2.0)
Initial stab at adding Action Cable to rails/master
2015-12-14 23:38:37 +08:00
puma
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-19 00:30:25 +08:00
qu-rails!
qu-redis
que
implement `provider_job_id` for `queue_classic`. The latest, currently unreleased, version of queue_classic is required for this to work. See https://github.com/QueueClassic/queue_classic/pull/262 for more details.
2015-08-13 15:56:06 +08:00
queue_classic!
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-19 00:30:25 +08:00
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 17:20:53 +08: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-19 00:30:25 +08:00
resque
resque-scheduler
run against edge sass to eliminate circular require warnings
2015-09-30 22:42:31 +08:00
sass!
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-19 00:30:25 +08:00
sdoc (~> 0.4.0)
sequel
sidekiq
Unlock sneakers adapter version
2015-04-26 15:44:18 +08:00
sneakers
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-19 00:30:25 +08:00
sqlite3 (~> 1.3.6)
stackprof
Updated Gemfile.lock with latest change related to sucker_punch dependency - Followup of https://github.com/rails/rails/commit/bc194937ad6c1fa12bca73cfc05de39a97ba783d.
2016-01-03 19:51:00 +08:00
sucker_punch (< 2.0)
Use released turbolinks in the test suite
2015-12-17 22:37:03 +08:00
turbolinks
Ruby 2.2.3 in windows need nokogiri 1.6.7.rc3 as it's the only version having correct pre-compiled so
2015-09-12 22:04:31 +08:00
tzinfo-data
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-19 00:30:25 +08:00
uglifier (>= 1.3.0)
w3c_validators
Generate Bundler 1.10.1 lockfile
2015-05-29 13:40:29 +08:00
BUNDLED WITH
Add mysql back to the Gemfile I didn't mean to commit that!
2015-12-17 04:59:00 +08:00
1.11.2