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

384 lines
8.7 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
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 20:47:24 +08:00
GIT
remote: git://github.com/mikel/mail.git
Upgrade all the gems
2015-10-21 01:58:57 +08:00
revision: 9c313a401729b9aa9177878836829a61adf67b54
Add master branch to github gems to be able to use local clones
2015-09-01 19:44:32 +08:00
branch: master
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 20:47:24 +08:00
specs:
mail (2.6.3.edge)
mime-types (>= 1.16, < 3)
point at rack master
2015-08-21 04:43:57 +08:00
GIT
remote: git://github.com/rack/rack.git
Upgrade all the gems
2015-10-21 01:58:57 +08:00
revision: 35599cfc2751e0ee611c0ff799924b8e7fe0c0b4
Add master branch to github gems to be able to use local clones
2015-09-01 19:44:32 +08:00
branch: master
point at rack master
2015-08-21 04:43:57 +08:00
specs:
rack (2.0.0.alpha)
json
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/rails/arel.git
Upgrade all the gems
2015-10-21 01:58:57 +08:00
revision: 3c429c5d86e9e2201c2a35d934ca6a8911c18e69
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
branch: master
specs:
arel (7.0.0.alpha)
Add gemfile entry for GlobalID until a new release is cut.
2015-07-05 20:50:33 +08:00
GIT
remote: git://github.com/rails/globalid.git
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
revision: 1d8fca667740570d204fd955a0bd39ac539bac7f
Add master branch to github gems to be able to use local clones
2015-09-01 19:44:32 +08:00
branch: master
Add gemfile entry for GlobalID until a new release is cut.
2015-07-05 20:50:33 +08:00
specs:
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
globalid (0.3.6)
Add gemfile entry for GlobalID until a new release is cut.
2015-07-05 20:50:33 +08:00
activesupport (>= 4.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
GIT
remote: git://github.com/rails/jquery-rails.git
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
revision: 04fcfa29b859eef9479f89b6a799d00212902385
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
branch: master
specs:
Add master branch to github gems to be able to use local clones
2015-09-01 19:44:32 +08:00
jquery-rails (4.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
rails-dom-testing (~> 1.0)
railties (>= 4.2.0)
thor (>= 0.14, < 2.0)
Migrate to Sprockets 4.
2015-08-05 21:14:09 +08:00
GIT
remote: git://github.com/rails/sass-rails.git
Upgrade all the gems
2015-10-21 01:58:57 +08:00
revision: 6e4eee736bcbfa5b2962467673c7a51abf434c67
Migrate to Sprockets 4.
2015-08-05 21:14:09 +08:00
branch: master
specs:
sass-rails (6.0.0)
railties (>= 4.0.0, < 5.0)
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
sass (~> 3.4)
Migrate to Sprockets 4.
2015-08-05 21:14:09 +08:00
sprockets (>= 4.0)
sprockets-rails (< 4.0)
Use latest sprockets-rails on internal dev
2015-04-26 23:42:13 +08:00
GIT
remote: git://github.com/rails/sprockets-rails.git
Upgrade all the gems
2015-10-21 01:58:57 +08:00
revision: 93a45b1c463a063ec7cf4d160107b67aa3db7a1a
Use latest sprockets-rails on internal dev
2015-04-26 23:42:13 +08:00
branch: master
specs:
Eliminate overlapping `app/assets` load path * Move `app/assets/manifest.js` to `app/assets/config/manifest.js`. Avoid the suggestion that you can/should deep-link `stylesheets/foo`. * Pull in all toplevel stylesheets and JavaScripts, not just `application.js` and `.css`. Demonstrate how to use `link_directory` with a specified `.js`/`.css` type. * Fix RAILS_ENV handling in assets tests. * Shush warnings spam from third-party libs that distract from tests.
2015-09-28 05:34:13 +08:00
sprockets-rails (3.0.0.beta3)
Use latest sprockets-rails on internal dev
2015-04-26 23:42:13 +08:00
actionpack (>= 4.0)
activesupport (>= 4.0)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
sprockets (>= 3.0.0)
Use latest sprockets-rails on internal dev
2015-04-26 23:42:13 +08:00
Migrate to Sprockets 4.
2015-08-05 21:14:09 +08:00
GIT
remote: git://github.com/rails/sprockets.git
Upgrade all the gems
2015-10-21 01:58:57 +08:00
revision: 5a77f8b007b8ec61edd783c48baf9d971f1c684d
Migrate to Sprockets 4.
2015-08-05 21:14:09 +08:00
branch: master
specs:
sprockets (4.0.0)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
rack (>= 1, < 3)
Migrate to Sprockets 4.
2015-08-05 21:14:09 +08:00
Use master version of Turbolinks gem Since `alias_method_chain` is deprecated we need to use the master version of the Turbolinks gem as it has support for using `Module#prepend`.
2015-09-18 13:54:27 +08:00
GIT
remote: git://github.com/rails/turbolinks.git
Upgrade all the gems
2015-10-21 01:58:57 +08:00
revision: 83d4b3d2c52a681f07900c28adb28bc8da604733
Use master version of Turbolinks gem Since `alias_method_chain` is deprecated we need to use the master version of the Turbolinks gem as it has support for using `Module#prepend`.
2015-09-18 13:54:27 +08:00
branch: master
specs:
turbolinks (3.0.0)
coffee-rails
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
Upgrade all the gems
2015-10-21 01:58:57 +08:00
revision: 4e3e1d5684cc29073a507578fc977434ff488c93
run against edge sass to eliminate circular require warnings
2015-09-30 22:42:31 +08:00
branch: stable
specs:
Upgrade all the gems
2015-10-21 01:58:57 +08:00
sass (3.4.19)
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:
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)
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)
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
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-08 01:48:06 +08: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-19 00:30:25 +08: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)
Require only necessary concurrent-ruby classes.
2015-11-03 10:30:50 +08:00
concurrent-ruby (~> 1.0.0.pre5, < 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
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)
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)
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)
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
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 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)
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
backburner (1.1.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)
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-x64-mingw32)
bcrypt (3.1.10-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)
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)
amq-protocol (>= 2.0.0)
point at rack master
2015-08-21 04:43:57 +08:00
byebug (6.0.2)
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
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
coffee-script-source (1.9.1.1)
Require only necessary concurrent-ruby classes.
2015-11-03 10:30:50 +08:00
concurrent-ruby (1.0.0.pre5)
Update Gemfile.lock
2015-08-10 11:30:03 +08:00
connection_pool (2.2.0)
dalli (2.7.4)
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)
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)
point at rack master
2015-08-21 04:43:57 +08:00
execjs (2.6.0)
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)
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)
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 listen to 3.0.4 3.0.3 has a bug in OS X.
2015-11-04 22:57:31 +08:00
listen (3.0.4)
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)
metaclass (0.0.4)
Add method_source to gemfile
2015-01-24 09:34:43 +08:00
method_source (0.8.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
mime-types (2.6.2)
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
mini_portile (0.7.0.rc4)
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)
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
mysql (2.9.1)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
mysql2 (0.4.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
nokogiri (1.6.7.rc3)
mini_portile (~> 0.7.0.rc4)
pg (0.18.3)
dup the request and mutate its headers object. duping the request will dup it's underlying env hash.
2015-08-22 07:40:53 +08:00
psych (2.0.15)
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)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
racc (1.4.13)
rack-cache (1.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
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)
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.2.1)
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)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
rufus-scheduler (3.1.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
sdoc (0.4.1)
json (~> 1.7, >= 1.7.7)
rdoc (~> 4.0)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
sequel (4.27.0)
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)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
sidekiq (3.5.1)
celluloid (~> 0.17.2)
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)
redis-namespace (~> 1.5, >= 1.5.2)
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)
Upgrade all the gems
2015-10-21 01:58:57 +08:00
sqlite3 (1.3.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
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
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
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)
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-07 07:35:02 +08: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-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
Add gemfile entry for GlobalID until a new release is cut.
2015-07-05 20:50:33 +08:00
globalid!
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
jquery-rails!
json
kindlerb (= 0.1.1)
upgrade listen to 3.0.4 3.0.3 has a bug in OS X.
2015-11-04 22:57:31 +08:00
listen (~> 3.0.4)
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 20:47:24 +08: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-19 00:30:25 +08:00
minitest (< 5.3.4)
mocha (~> 0.14)
mysql (>= 2.9.0)
Use released mysql2
2015-09-09 01:01:04 +08:00
mysql2 (>= 0.4.0)
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
nokogiri (>= 1.6.7.rc3)
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)
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)
point at rack master
2015-08-21 04:43:57 +08:00
rack!
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-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!
Migrate to Sprockets 4.
2015-08-05 21:14:09 +08:00
sass-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
sdoc (~> 0.4.0)
sequel
sidekiq
Unlock sneakers adapter version
2015-04-26 15:44:18 +08:00
sneakers
Eliminate overlapping `app/assets` load path * Move `app/assets/manifest.js` to `app/assets/config/manifest.js`. Avoid the suggestion that you can/should deep-link `stylesheets/foo`. * Pull in all toplevel stylesheets and JavaScripts, not just `application.js` and `.css`. Demonstrate how to use `link_directory` with a specified `.js`/`.css` type. * Fix RAILS_ENV handling in assets tests. * Shush warnings spam from third-party libs that distract from tests.
2015-09-28 05:34:13 +08:00
sprockets (~> 4.0)!
sprockets-rails (~> 3.0.0.beta3)!
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
sucker_punch
Use master version of Turbolinks gem Since `alias_method_chain` is deprecated we need to use the master version of the Turbolinks gem as it has support for using `Module#prepend`.
2015-09-18 13:54:27 +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
point at rack master
2015-08-21 04:43:57 +08:00
1.10.6