search

yegor256 / 0rsk

Online Risk Manager
https://www.0rsk.com
MIT License
20 stars 2 forks source link

Bump actionpack from 6.0.1 to 6.0.3.1 #62

Closed dependabot[bot] closed 4 years ago

dependabot[bot] commented 4 years ago

Bumps actionpack from 6.0.1 to 6.0.3.1.

Release notes

Sourced from actionpack's releases.

6.0.3

In this version, we fixed warnings when used with Ruby 2.7 across the entire framework.

Following are the list of other changes, per-framework.

Active Support

  • Array#to_sentence no longer returns a frozen string.

    Before:

    ['one', 'two'].to_sentence.frozen?
# => true

    After:

    ['one', 'two'].to_sentence.frozen?
# => false

    Nicolas Dular

  • Update ActiveSupport::Messages::Metadata#fresh? to work for cookies with expiry set when ActiveSupport.parse_json_times = true.

    Christian Gregg

Active Model

  • No changes.

Active Record

  • Recommend applications don't use the database kwarg in connected_to

    The database kwarg in connected_to was meant to be used for one-off scripts but is often used in requests. This is really dangerous because it re-establishes a connection every time. It's deprecated in 6.1 and will be removed in 6.2 without replacement. This change soft deprecates it in 6.0 by removing documentation.

    Eileen M. Uchitelle

  • Fix support for PostgreSQL 11+ partitioned indexes.

    Sebastián Palma

  • Add support for beginless ranges, introduced in Ruby 2.7.

    Josh Goodall

... (truncated)
Changelog

Sourced from actionpack's changelog.

Rails 6.0.3.1 (May 18, 2020)

  • [CVE-2020-8166] HMAC raw CSRF token before masking it, so it cannot be used to reconstruct a per-form token

  • [CVE-2020-8164] Return self when calling #each, #each_pair, and #each_value instead of the raw @parameters hash

Rails 6.0.3 (May 06, 2020)

  • Include child session assertion count in ActionDispatch::IntegrationTest

    IntegrationTest#open_session uses dup to create the new session, which meant it had its own copy of @assertions. This prevented the assertions from being correctly counted and reported.

    Child sessions now have their attr_accessor overriden to delegate to the root session.

    Fixes #32142

    Sam Bostock

Rails 6.0.2.2 (March 19, 2020)

  • No changes.

Rails 6.0.2.1 (December 18, 2019)

  • Fix possible information leak / session hijacking vulnerability.

    The ActionDispatch::Session::MemcacheStore is still vulnerable given it requires the gem dalli to be updated as well.

    CVE-2019-16782.

Rails 6.0.2 (December 13, 2019)

  • Allow using mountable engine route helpers in System Tests.

    Chalo Fernandez

Commits
  • 34991a6 Preparing for 6.0.3.1 release
  • 2c8fe2a bumping version, updating changelog
  • 0ad524a update changelog
  • 29aa538 HMAC raw CSRF token before masking it, so it cannot be used to reconstruct a ...
  • b3230c5 Return self when calling #each, #each_pair, and #each_value instead of the ra...
  • b738f19 Preparing for 6.0.3 release
  • 509b9da Preparing for 6.0.3.rc1 release
  • b60571e Merge pull request #38864 from abhaynikam/replace-mailing-list-url
  • 639e646 Add CHANGELOG entry to 6.0.2.2
  • ff380b5 Merge branch '6-2-sec' into 6-0-stable
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/yegor256/0rsk/network/alerts).
0crat commented 4 years ago

@yegor256/z please, pay attention to this pull request

0crat commented 4 years ago

There is an unrecoverable failure on my side. Please, submit it here:

PID: 4@2be63c13-446f-4aaf-b035-a2d81942b365, thread: PQ-C3RFVLU72
com.jcabi.xml.StrictXML[124] java.lang.IllegalArgumentException: 2 error(s) in XML document: -1:-1: cvc-pattern-valid: Value 'dependabot[bot]' is not facet-valid with respect to pattern '[a-z0-9\-]{3,}' for type 'login'.;-1:-1: cvc-type.3.1.3: The value 'dependabot[bot]' of element 'login' is not valid.

0.53.14: CID: 1b764a09-f64e-4331-8494-c47b459398f5, Type: "Job was added to WBS"

0crat commented 4 years ago

@yegor256/z everybody who has role REV is banned at #62; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

0crat commented 4 years ago

@yegor256/z everybody who has role REV is banned at #62; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

0crat commented 4 years ago

@yegor256/z everybody who has role REV is banned at #62; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

0crat commented 4 years ago

@yegor256/z everybody who has role REV is banned at #62; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

0crat commented 4 years ago

@yegor256/z everybody who has role REV is banned at #62; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

0crat commented 4 years ago

@yegor256/z everybody who has role REV is banned at #62; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

dependabot[bot] commented 4 years ago

Superseded by #64.

0crat commented 4 years ago

Job gh:yegor256/0rsk#62 is not assigned, can't get performer

0crat commented 4 years ago

Pull request #62 was not merged, no payment for ARC, see §28