Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency rack to v3.1.6 #79

Merged
merged 1 commit into from
Jul 6, 2024
Merged

Update dependency rack to v3.1.6 #79

merged 1 commit into from
Jul 6, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 11, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
rack (changelog) '3.0.11' -> '3.1.6' age adoption passing confidence

Release Notes

rack/rack (rack)

v3.1.6

Compare Source

  • Fix several edge cases in Rack::Request#parse_http_accept_header's implementation. (#​2226, [@​ioquatix])

v3.1.5

Compare Source

Security

v3.1.4

Compare Source

Fixed

v3.1.3

Compare Source

v3.1.2

Compare Source

v3.1.1

Compare Source

  • Oops! I shouldn't have shipped that

v3.1.0

Rack v3.1 is primarily a maintenance release that removes features deprecated in Rack v3.0. Alongside these removals, there are several improvements to the Rack SPEC, mainly focused on enhancing input and output handling. These changes aim to make Rack more efficient and align better with the requirements of server implementations and relevant HTTP specifications.

SPEC Changes
Added
Changed
  • MIME type for JavaScript files (.js) changed from application/javascript to text/javascript (1bd0f15, [@​ioquatix])
  • Update MIME types associated to .ttf, .woff, .woff2 and .otf extensions to use mondern font/* types. (#​2065, [@​davidstosik])
  • Rack::Utils.escape_html is now delegated to CGI.escapeHTML. ' is escaped to #​39; instead of #x27;. (decimal vs hexadecimal) (#​2099, @​JunichiIto)
  • Clarify use of @buffered and only update content-length when Rack::Response#finish is invoked. (#​2149, [@​ioquatix])
Deprecated
  • Deprecate automatic cache invalidation in Request#{GET,POST} (#​2073, [@​jeremyevans])
  • Only cookie keys that are not valid according to the HTTP specifications are escaped. We are planning to deprecate this behaviour, so now a deprecation message will be emitted in this case. In the future, invalid cookie keys may not be accepted. (#​2191, [@​ioquatix])
  • Rack::Logger is deprecated. (#​2197, [@​ioquatix])
  • Add fallback lookup and deprecation warning for obsolete status symbols. (#​2137, @​wtn)
Removed
  • Remove deprecated Rack::Auth::Digest with no replacement. (#​1966, [@​ioquatix])
  • Remove deprecated Rack::Cascade::NotFound with no replacement. (#​1966, [@​ioquatix])
  • Remove deprecated Rack::Chunked with no replacement. (#​1966, [@​ioquatix])
  • Remove deprecated Rack::File, use Rack::Files instead. (#​1966, [@​ioquatix])
  • Remove deprecated Rack::QueryParser key_space_limit parameter with no replacement. (#​1966, [@​ioquatix])
  • Remove deprecated Rack::Response#header, use Rack::Response#headers instead. (#​1966, [@​ioquatix])
  • Remove deprecated cookie methods from Rack::Utils: add_cookie_to_header, make_delete_cookie_header, add_remove_cookie_to_header. (#​1966, [@​ioquatix])
  • Remove deprecated Rack::Utils::HeaderHash. (#​1966, [@​ioquatix])
  • Remove deprecated Rack::VERSION, Rack::VERSION_STRING, Rack.version, use Rack.release instead. (#​1966, [@​ioquatix])
  • Remove non-standard status codes 306, 509, & 510 and update descriptions for 413, 422, & 451. (#​2137, @​wtn)
  • Remove any dependency on transfer-encoding: chunked. (#​2195, [@​ioquatix])
Fixed

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title Update dependency rack to v3.1.0 Update dependency rack to v3.1.2 Jun 11, 2024
@renovate renovate bot changed the title Update dependency rack to v3.1.2 Update dependency rack to v3.1.3 Jun 12, 2024
@yegor256
Copy link
Owner

@rultor please, try to merge, since 7 checks have passed

@rultor
Copy link
Collaborator

rultor commented Jun 19, 2024

@rultor please, try to merge, since 7 checks have passed

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor
Copy link
Collaborator

rultor commented Jun 19, 2024

@rultor please, try to merge, since 7 checks have passed

@renovate[bot] @yegor256 Oops, I failed. You can see the full log here (spent 9min)

2024-06-19 20:12:43.246 UTC [1786] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
2024-06-19 20:12:43.246 UTC [1786] LOG:  could not open temporary statistics file "pg_stat_tmp/global.tmp": No such file or directory
2024-06-19 20:12:43.573 UTC [1780] LOG:  could not open file "postmaster.pid": No such file or directory
2024-06-19 20:12:43.574 UTC [1780] LOG:  performing immediate shutdown because data directory lock file is invalid
2024-06-19 20:12:43.575 UTC [1780] LOG:  received immediate shutdown request
2024-06-19 20:12:43.575 UTC [1780] LOG:  could not open file "postmaster.pid": No such file or directory
2024-06-19 20:12:43.578 UTC [1786] LOG:  could not open temporary statistics file "pg_stat/global.tmp": No such file or directory
2024-06-19 20:12:43.585 UTC [1780] LOG:  database system is shut down
INFO 6/19/24, 8:12 PM: liquibase: Successfully acquired change log lock
INFO 6/19/24, 8:12 PM: liquibase: Creating database history table with name: databasechangelog
INFO 6/19/24, 8:12 PM: liquibase: Reading from databasechangelog
INFO 6/19/24, 8:12 PM: liquibase: /home/r/repo/test-resources/master.xml: 001-initial-schema.xml::01::yegor256: Custom SQL executed
INFO 6/19/24, 8:12 PM: liquibase: /home/r/repo/test-resources/master.xml: 001-initial-schema.xml::01::yegor256: ChangeSet 001-initial-schema.xml::01::yegor256 ran successfully in 9ms
INFO 6/19/24, 8:12 PM: liquibase: Successfully released change log lock
\u001b[0m\u001b[0mD: PostgreSQL pool started with 1 connections
D: INSERT INTO book (title) VALUES ($1) RETURNING id: 2ms / 3140
\u001b[32m.\u001b[0m

Finished in 118.193362s, 0.0931 runs/s, 0.0846 assertions/s.
11 runs, 10 assertions, 0 failures, 1 errors, 0 skips
2024-06-19 20:12:48.410 UTC [2094] LOG:  received smart shutdown request
2024-06-19 20:12:48.411 UTC [2094] LOG:  could not open file "postmaster.pid": No such file or directory
PostgreSQL killed in PID 2094
2024-06-19 20:12:48.414 UTC [2068] LOG:  received smart shutdown request
2024-06-19 20:12:48.414 UTC [2068] LOG:  could not open file "postmaster.pid": No such file or directory
PostgreSQL killed in PID 2068
PostgreSQL killed in PID 2041
2024-06-19 20:12:48.419 UTC [1976] LOG:  received smart shutdown request
2024-06-19 20:12:48.419 UTC [1976] LOG:  could not open file "postmaster.pid": No such file or directory
PostgreSQL killed in PID 1976
2024-06-19 20:12:48.422 UTC [1910] LOG:  received smart shutdown request
2024-06-19 20:12:48.423 UTC [1910] LOG:  could not open file "postmaster.pid": No such file or directory
PostgreSQL killed in PID 1910
PostgreSQL killed in PID 1845
PostgreSQL killed in PID 1780
PostgreSQL killed in PID 1710
PostgreSQL killed in PID 1640
PostgreSQL killed in PID 1615
Coverage report generated for Unit Tests to /home/r/repo/coverage. 175 / 189 LOC (92.59%) covered.
2024-06-19 20:12:48.464 UTC [1976] LOG:  background worker "logical replication launcher" (PID 1983) exited with exit code 1
2024-06-19 20:12:48.465 UTC [1978] LOG:  shutting down
2024-06-19 20:12:48.465 UTC [1978] PANIC:  could not open file "/tmp/test20240619-1598-w1y9ns/pgsql/global/pg_control": No such file or directory
2024-06-19 20:12:48.485 UTC [2094] LOG:  background worker "logical replication launcher" (PID 2101) exited with exit code 1
2024-06-19 20:12:48.490 UTC [2096] LOG:  shutting down
2024-06-19 20:12:48.490 UTC [2096] PANIC:  could not open file "/tmp/test20240619-1598-uyccab/pgsql/global/pg_control": No such file or directory
2024-06-19 20:12:48.521 UTC [1910] LOG:  background worker "logical replication launcher" (PID 1917) exited with exit code 1
2024-06-19 20:12:48.526 UTC [1912] LOG:  shutting down
2024-06-19 20:12:48.527 UTC [1912] PANIC:  could not open file "/tmp/test20240619-1598-7gr088/pgsql/global/pg_control": No such file or directory
2024-06-19 20:12:48.573 UTC [2068] LOG:  background worker "logical replication launcher" (PID 2075) exited with exit code 1
2024-06-19 20:12:48.582 UTC [2070] LOG:  shutting down
2024-06-19 20:12:48.582 UTC [2070] PANIC:  could not open file "/tmp/test20240619-1598-99ucg4/pgsql/global/pg_control": No such file or directory
rake aborted!
Command failed with status (1)
/usr/local/rvm/gems/ruby-3.2.2/gems/rake-13.2.1/exe/rake:27:in `<top (required)>'
/usr/local/rvm/gems/ruby-3.2.2/bin/ruby_executable_hooks:22:in `eval'
/usr/local/rvm/gems/ruby-3.2.2/bin/ruby_executable_hooks:22:in `<main>'
Tasks: TOP => default => test
(See full trace by running task with --trace)
container 2915bd9a5cb832e400b603d5fd4eb2673b8920425adde3046555c5d12944c3e6 is dead
Wed Jun 19 20:13:01 UTC 2024

@renovate renovate bot changed the title Update dependency rack to v3.1.3 Update dependency rack to v3.1.4 Jun 22, 2024
@renovate renovate bot force-pushed the renovate/rack-3.x branch 2 times, most recently from 8c189f1 to 5755418 Compare July 2, 2024 08:00
@renovate renovate bot changed the title Update dependency rack to v3.1.4 Update dependency rack to v3.1.5 Jul 2, 2024
@renovate renovate bot changed the title Update dependency rack to v3.1.5 Update dependency rack to v3.1.6 Jul 2, 2024
@yegor256 yegor256 merged commit 17e2094 into master Jul 6, 2024
7 checks passed
@renovate renovate bot deleted the renovate/rack-3.x branch July 6, 2024 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants