aboutsummaryrefslogtreecommitdiffstats
path: root/Gemfile.lock
Commit message (Collapse)AuthorAgeFilesLines
* Add gemfile entry for GlobalID until a new release is cut.Kasper Timm Hansen2015-07-051-3/+9
|
* Update bundler to v1.10.4Tim Rogers2015-06-171-1/+1
|
* let's use the latest bundler version.Yves Senn2015-06-131-1/+1
|
* Ensure symbols passed to `select` are always quotedSean Griffin2015-05-301-1/+1
| | | | | | | | | | | | | | | | | Our general contract in Active Record is that strings are assumed to be SQL literals, and symbols are assumed to reference a column. If a from clause is given, we shouldn't include the table name, but we should still quote the value as if it were a column. Upon fixing this, the tests were still failing on SQLite. This was because the column name being returned by the query was `"\"join\""` instead of `"join"`. This is actually a bug in SQLite that was fixed a long time ago, but I was using the version of SQLite included by OS X which has this bug. Since I'm guessing this will be a common case for contributors, I also added an explicit check with a more helpful error message. Fixes #20360
* Generate Bundler 1.10.1 lockfileSamuel E. Giddins2015-05-281-0/+3
|
* Unlock sneakers adapter versionSemyon Pupkov2015-04-281-7/+7
|
* Use latest sprockets-rails on internal devArthur Neves2015-04-261-7/+14
|
* Uncomment byebug in framework GemfileGodfrey Chan2015-04-241-0/+4
| | | | | | | | | | | | | | | 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)
* Gemfile: temporay pin "bcrypt" version and run "bundle update bcrypt" on LinuxToshi MARUYAMA2015-04-091-1/+10
| | | | | | | 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
* redcarpet 3.2.2 has an XSS vulnerabilityAkira Matsuda2015-04-091-2/+2
| | | | see: http://www.openwall.com/lists/oss-security/2015/04/07/11
* Remove old mri platform entries from our GemfileCarlos Antonio da Silva2015-04-011-2/+0
| | | | | | | | | | Since we now only support Ruby 2.2+, we can safely remove the old mri entries from the Gemfile. This also allows us not to lock to a specific bundler version, since :mri_22 was defined only on 1.7.11. Closes #19611.
* Test using sprockets 3Rafael Mendonça França2015-03-291-6/+3
|
* method_source needs to be a hard dependency on railtiesArthur Neves2015-03-191-1/+1
|
* Add method_source to gemfileArthur Neves2015-03-181-0/+2
|
* Use the released gemRafael Mendonça França2015-03-101-8/+2
|
* Let strip_tags leave HTML escaping to Rails.Kasper Timm Hansen2015-03-101-4/+10
| | | | Prevents double escaping errors, such as "&" becoming "&".
* Fixed ActiveJob integration testsCristian Bica2015-03-051-0/+4
|
* Test against the mail gem's edgeRobin Dupret2015-03-021-2/+8
| | | | | | | | | | 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.
* Bump rack-test to fix nil values being sent to `parse_nested_query`eileencodes2015-03-011-1/+1
| | | | | | | | | | 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.
* Format the time string according to the precision of the time columnRyuta Kamizono2015-02-201-1/+1
| | | | It is also necessary to format a time column like a datetime column.
* Track Gemfile.lock at the repositoryRafael Mendonça França2015-02-181-0/+281
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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 08:01:27 +0000