aboutsummaryrefslogtreecommitdiffstats
path: root/activesupport/activesupport.gemspec
Commit message (Collapse)AuthorAgeFilesLines
* improves the reloading disabled error messageXavier Noria2019-04-111-1/+1
| | | | | | | | The original message from Zeitwerk is "can't reload, please call loader.enable_reloading before setup (Zeitwerk::Error)", which is not very informative for Rails programmers. Rails should err with a message worded in terms of its interface.
* depend on Zeitwerk 2.1.0Xavier Noria2019-04-091-1/+1
|
* depend on Zeitwerk 2Xavier Noria2019-04-071-1/+1
|
* bumps Zeitwerk and BootsnapXavier Noria2019-03-261-1/+1
|
* Depend on Zeitwerk 1.4.2Xavier Noria2019-03-231-1/+1
|
* depend on Zeitwerk 1.4.0Xavier Noria2019-03-191-1/+1
|
* bumps ZeitwerkXavier Noria2019-03-141-1/+1
|
* bump Zeitwerk to 1.3.3Xavier Noria2019-03-111-1/+1
|
* Fix links in gemspec and docs from http to https.Abhay Nikam2019-03-091-1/+1
|
* Bump ZeitwerkXavier Noria2019-03-061-1/+1
|
* Upgrade Zeitwerk to 1.3.1Xavier Noria2019-02-231-1/+1
|
* bump ZeitwerkXavier Noria2019-02-211-1/+1
|
* upgrades Zeitwerk to 1.2.0Xavier Noria2019-02-171-1/+1
|
* Replace autoloader accessors with Rails.autoloaders.{main,once}Xavier Noria2019-02-141-1/+1
| | | | | | | | | | | | | | | | Rails.autoloader and Rails.once_autoloader was just tentative API good enough for a first patch. Rails.autoloader is singular and does not convey in its name that there is another autoloader. That might be confusing, for example if you set a logger and miss traces. On the other hand, the name `once_autoloader` is very close to being horrible. Rails.autoloaders.main and Rails.autoloaders.once read better for my taste, and have a nice symmetry. Also, both "main" and "once" are four letters long, short and same length. They are tagged as "rails.main" and "rails.once", respectively. References #35235.
* Let Zeitwerk be a dependency of Active SupportXavier Noria2019-02-131-3/+4
| | | | | Zeitwerk is a strong dependency, planned to replace AS::Dependencies. A line in the generated Gemfile does not convey this as much.
* Revert "Revert "Merge pull request #34387 from ↵Kasper Timm Hansen2019-01-081-0/+3
| | | | | | | | yhirano55/rails_info_properties_json"" I reverted the wrong commit. Damn it. This reverts commit f66a977fc7ae30d2a07124ad91924c4ee638a703.
* Revert "Merge pull request #34387 from yhirano55/rails_info_properties_json"Kasper Timm Hansen2019-01-081-3/+0
| | | | | | | | | | | We had a discussion on the Core team and we don't want to expose this information as a JSON endpoint and not by default. It doesn't make sense to expose this JSON locally and this controller is only accessible in dev, so the proposed access from a production app seems off. This reverts commit 8eaffe7e89719ac62ff29c2e4208cfbeb1cd1c38, reversing changes made to b6e4305c3bca4c673996d0af9db0f4cfbf50215e.
* Require Ruby 2.5 for Rails 6.Kasper Timm Hansen2018-12-191-1/+1
| | | | | | | | | | Generally followed the pattern for https://github.com/rails/rails/pull/32034 * Removes needless CI configs for 2.4 * Targets 2.5 in rubocop * Updates existing CHANGELOG entries for fewer merge conflicts * Removes Hash#slice extension as that's inlined on Ruby 2.5. * Removes the need for send on define_method in MethodCallAssertions.
* Amend CVE note and security guide section wordingsGannon McGibbon2018-11-061-3/+3
| | | | | | | Reword first sentence of dep management and CVE section of security guide. Also, reword and move gemspec notes above deps. [ci skip]
* Add CVE note to security guide and gemspecsGannon McGibbon2018-11-061-0/+3
| | | | [ci skip]
* Rails 6 requires Ruby 2.4.1+Jeremy Daer2018-02-171-1/+1
| | | | | | Skipping over 2.4.0 to sidestep the `"symbol_from_string".to_sym.dup` bug. References #32028
* Remove support to Ruby 2.2Rafael Mendonça França2018-02-161-1/+1
| | | | Rails 6 will only support Ruby >= 2.3.
* Don't force people to upgrade i18n gemRafael Mendonça França2018-02-141-1/+1
|
* Bump i18n to 1.0Ryan Bigg2018-02-141-1/+1
|
* [Active Support] `rubocop -a --only Layout/EmptyLineAfterMagicComment`Koichi ITO2017-07-111-0/+1
|
* Use frozen-string-literal in ActiveSupportKir Shatrov2017-07-091-0/+1
|
* Revert "Merge pull request #29540 from kirs/rubocop-frozen-string"Matthew Draper2017-07-021-1/+0
| | | | | This reverts commit 3420a14590c0e6915d8b6c242887f74adb4120f9, reversing changes made to afb66a5a598ce4ac74ad84b125a5abf046dcf5aa.
* Enforce frozen string in RubocopKir Shatrov2017-07-011-0/+1
|
* Add source code and changelog links to gemspecsGrey Baker2017-06-281-0/+5
|
* Define path with __dir__bogdanvlviv2017-05-231-1/+1
| | | | | | ".. with __dir__ we can restore order in the Universe." - by @fxn Related to 5b8738c2df003a96f0e490c43559747618d10f5f
* applies new string literal convention in the gemspecsXavier Noria2016-08-061-16/+16
| | | | | The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
* Fix template resolver cache concurrency: "can't add a new key into hash ↵Jeremy Daer2016-05-021-1/+1
| | | | | | | | during iteration" Resolved by https://github.com/ruby-concurrency/concurrent-ruby/pull/529 Fixes #24627.
* revises the homepage URL in the gemspecs [ci skip]Xavier Noria2016-03-101-1/+1
| | | | References https://github.com/rails/homepage/issues/46.
* Remove unused dependencyMike Perham2016-02-031-1/+0
| | | railties uses method_source, activesupport does not. I assume code was refactored and the dependency wasn't removed.
* Remove json gem dependencyMike Perham2016-02-031-1/+0
| | | All modern Rubies ship JSON as part of stdlib. Using the gem actually hurts multi-platform support due to build difficulties on Windows.
* Using released concurrent-rubyRafael Mendonça França2015-11-161-1/+1
|
* Require only necessary concurrent-ruby classes.Jerry D'Antonio2015-11-041-1/+1
|
* Fixed concurrent-ruby warnings.Jerry D'Antonio2015-09-291-1/+1
| | | | | Bumped version of concurrent-ruby to 1.0.0.pre3, which fixes all interpreter warnings.
* Replaced `ThreadSafe::Map` with successor `Concurrent::Map`.Jerry D'Antonio2015-09-191-2/+1
| | | | | | | The thread_safe gem is being deprecated and all its code has been merged into the concurrent-ruby gem. The new class, Concurrent::Map, is exactly the same as its predecessor except for fixes to two bugs discovered during the merge.
* Initial implementation of ActiveJob AsyncAdapter.Jerry D'Antonio2015-08-251-1/+1
|
* Add method_source dependency to activesupportThomas Walpole2015-07-291-0/+1
|
* Replaced `ActiveSupport::Concurrency::Latch` with concurrent-ruby.Jerry D'Antonio2015-07-131-0/+1
| | | | | | | | | | The concurrent-ruby gem is a toolset containing many concurrency utilities. Many of these utilities include runtime-specific optimizations when possible. Rather than clutter the Rails codebase with concurrency utilities separate from the core task, such tools can be superseded by similar tools in the more specialized gem. This commit replaces `ActiveSupport::Concurrency::Latch` with `Concurrent::CountDownLatch`, which is functionally equivalent.
* Upgrade to Ruby 2.2.2Jon Atack2015-04-141-1/+1
| | | | and fix the grammar in the ruby_version_check.rb user message.
* Target Ruby 2.2.1 in gemspecsPeter Suschlik2015-03-091-1/+1
| | | | This is a follow-up to #19257
* Require Ruby 2.2 for Rails 5.0claudiob2014-12-261-1/+1
| | | | | Stems from [this comment](https://github.com/rails/rails/pull/18203#issuecomment-68138096) by @robin850 and by the blog post http://weblog.rubyonrails.org/2014/12/19/Rails-4-2-final
* Use released I18n 0.7.0Carlos Antonio da Silva2014-12-191-1/+1
|
* Merge pull request #18072 from exAspArk/thread_safe_gem_versionRafael Mendonça França2014-12-171-1/+1
|\ | | | | | | Use thread_safe gem version greater or equal to 0.3.4
| * use thread_safe gem version greater or equal to 0.3.4Evgeny Li2014-12-171-1/+1
|/
* Bump required Ruby version to 2.1.0claudiob2014-11-281-1/+1
| | | | | | | | | [This article](http://weblog.rubyonrails.org/2014/8/20/Rails-4-2-beta1/#maintenance-consequences-and-rails-5-0) states that: > Rails 5.0 is in most likelihood going to target Ruby 2.2. Before the exact minimum version is fully decided, @arthurnn [suggests](https://github.com/rails/rails/pull/17830#issuecomment-64940383) that **at least** version 2.1.0 **must** be required by the `gemspec` files.
* Use the released beta of i18nCarlos Antonio da Silva2014-08-181-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 19:19:42 +0000