Release 1.1.0

[HodaSalim]

Summary

Cuts the 1.1.0 release. Bumps lib/sift/version.rb from 1.0.1 to 1.1.0, adds the corresponding CHANGELOG.md entry, and removes an unused CircleCI SonarQube stub.

Why 1.1.0 (not 1.0.1)

The currently-staged 1.0.1 version (set in #67) includes a hard drop of Rails/ActiveRecord 6.1 support and raises the floor to activerecord >= 7.0. That's a backwards-incompatible dependency change for consumers, so a minor (or major) bump is more appropriate than a patch. Going with 1.1.0.

Planned contents of 1.1.0

Already merged:

• Migrate from Travis CI to GitHub Actions #67 — Migrate Travis → GitHub Actions, add Rails 7.1/7.2/8.0 appraisals, drop Rails 6.1

Pending merge before this PR is marked ready:

• Fix filter by boolean field #58 — Fix boolean filter being silently skipped when value is false
• Fix jsonb array filtering #77 — Fix NameError in JSONB filtering when value is an Array
• Reorganize documentation into docs/ directory #68 — Reorganize documentation into docs/ directory
• Add allow_nil option for IS NULL filtering on non-JSONB types #84 — Add allow_nil: true option to filter_on for IS NULL filtering on non-JSONB column types
• adding support to the where handler for jsonb for date ranges in the … #83 — Add date range filtering on JSONB keys, using the same ... range format as other filters

Docs and CHANGELOG.md entries for #84 and #83 are already included on this release branch (see docs/filters.md). If any of these don't land in this release, remove the corresponding bullet from CHANGELOG.md (and the matching docs sections) before marking ready for review.

Also: CircleCI cleanup

Removes .circleci/config.yml, which was added in #67 only as a stub to satisfy a required sonarqube_analysis branch-protection check inherited from when this repo lived under the procore org. No SonarQube analysis was actually being performed, and no other procore-oss Ruby gem has SonarQube configured.

Release mechanics

Once #72 (auto-release workflow) is merged, merging this PR to main will trigger the workflow to publish procore-sift 1.1.0 to RubyGems (because lib/sift/version.rb changed). Confirm the RUBY_GEMS_API_KEY secret is configured on the repo before merging.

If #72 is not merged first, a maintainer with push rights on rubygems.org will need to run gem build sift.gemspec && gem push procore-sift-1.1.0.gem manually after merge.

Checklist

• PRs Fix jsonb array filtering #77, Fix filter by boolean field #58, Reorganize documentation into docs/ directory #68, Add allow_nil option for IS NULL filtering on non-JSONB types #84, adding support to the where handler for jsonb for date ranges in the … #83 are merged (or removed from changelog)
• Add GitHub Actions release workflow for gem publishing #72 (auto-release workflow) is merged, OR a maintainer is lined up to publish manually
• RUBY_GEMS_API_KEY secret is configured on the repo
• sonarqube_analysis required check removed from main branch protection
• Convert from draft → ready for review
• Two reviewer approvals per CONTRIBUTING.md
• After merge + publish: git tag v1.1.0 && git push origin v1.1.0 and create a matching GitHub Release

🤖 Generated with Claude Code

[github-actions]

This PR is stale because it has been open 20 days with no activity. Replace the no-pr-activity label with a work-in-progress label or comment or this will be closed in 5 days.

[github-actions]

This PR was closed because it has been stalled for 5 days with no activity.