Skip to content

Commit

Permalink
Release version 0.4.0
Browse files Browse the repository at this point in the history
This release includes three potentially breaking changes:
- Support for Ruby 2.6 dropped
- Support for ActiveRecord 5.x dropped
- Changed timestamp field cursor logic for more consistent pagination

All changes in this version:

Changed:
- BREAKING: Raised minimum required Ruby version to 2.7
- BREAKING: Raised minimum required `activerecord` version to 6.0

Added:
- Test against Ruby version 3.2

Fixed:
- BREAKING: Ensure timestamp `order_by` fields (like `created_at`) will
  paginate results by honoring timestamp order down to microsecond
  resolution on comparison. This was done by changing the cursor logic
  for timestamp fields, which means that the cursor strings change from
  version 0.3.0 to 0.4.0 and old cursors cannot be decoded by the new
  gem version anymore.
  • Loading branch information
nicolas-fricke committed Oct 6, 2023
1 parent fd799d4 commit 83b3c70
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 6 deletions.
8 changes: 5 additions & 3 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,15 +14,17 @@ These are the latest changes on the project's `master` branch that have not yet
Follow the same format as previous releases by categorizing your feature into "Added", "Changed", "Deprecated", "Removed", "Fixed", or "Security".
--->

## [0.4.0] - 2023-10-06

### Changed
- Raised minimum required Ruby version to 2.7
- Raised minimum required `activerecord` version to 6.0
- **Breaking change:** Raised minimum required Ruby version to 2.7
- **Breaking change:** Raised minimum required `activerecord` version to 6.0

### Added
- Test against Ruby version 3.2

### Fixed
- Ensure timestamp `order_by` fields will have expected paginated results by honoring of timestamps down to microsecond resolution on comparison.
- **Breaking change:** Ensure timestamp `order_by` fields (like `created_at`) will paginate results by honoring timestamp order down to microsecond resolution on comparison. This was done by changing the cursor logic for timestamp fields, which means that the cursors strings change from version 0.3.0 to 0.4.0 and old cursors cannot be decoded by the new gem version anymore.

## [0.3.0] - 2022-07-08

Expand Down
4 changes: 2 additions & 2 deletions Gemfile.lock
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
PATH
remote: .
specs:
rails_cursor_pagination (0.3.0)
rails_cursor_pagination (0.4.0)
activerecord (>= 6.0)

GEM
Expand Down Expand Up @@ -35,7 +35,7 @@ GEM
concurrent-ruby (~> 1.0)
json (2.6.3)
language_server-protocol (3.17.0.3)
minitest (5.19.0)
minitest (5.20.0)
mutex_m (0.1.2)
mysql2 (0.5.5)
parallel (1.23.0)
Expand Down
2 changes: 1 addition & 1 deletion lib/rails_cursor_pagination/version.rb
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# frozen_string_literal: true

module RailsCursorPagination
VERSION = '0.3.0'
VERSION = '0.4.0'
end

0 comments on commit 83b3c70

Please sign in to comment.