[ruby] Update pagy 6.2.0 → 6.3.0 (minor) #2355
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ pagy (6.2.0 → 6.3.0) · Repo · Changelog
Release Notes
6.3.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
Merge branch 'dev'Version 6.3.0DEV: Edited run configurationsCalendar improvements:Docs: fixes and improvements, code indentationDocs: explain: pagy + retype, add contribution instructions (#572)Added README file with note about dependency fixes (to be removed)Chore: bump rickstaa/action-create-tag from 1.7.1 to 1.7.2 (#575)Added ruby 3.3 to CIUpdated RubyMine run-configurationsUpdated node modules (dev on node 20)Updated Gemfile and fixed new rubocop complaintsDocs: fix for broken linkDoc: small improvementDocs: Better doc for Javscript setup buildersDocs: Improved Javascript Setup and removed unlinked and now redundant README from javascript dirChore: bump rickstaa/action-create-tag from 1.6.6 to 1.7.1 (#568)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands