Skip to content

Release 1.1.0#75

Open
HodaSalim wants to merge 2 commits into
mainfrom
release/1.1.0
Open

Release 1.1.0#75
HodaSalim wants to merge 2 commits into
mainfrom
release/1.1.0

Conversation

@HodaSalim

@HodaSalim HodaSalim commented May 11, 2026

Copy link
Copy Markdown
Contributor

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:

Pending merge before this PR is marked ready:

If any of these don't land in this release, remove the corresponding bullet from CHANGELOG.md 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

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Hoda Salim <hoda.s.salim@gmail.com>
The stub was added in #67 only to satisfy a required branch-protection check
left over from when sift lived under the procore org. SonarQube isn't actually
configured for this repo and no other procore-oss Ruby gem has SonarQube.
Removing the file requires the corresponding required check to be removed
from branch protection on main.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Hoda Salim <hoda.s.salim@gmail.com>
@github-actions

github-actions Bot commented Jun 1, 2026

Copy link
Copy Markdown

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

github-actions Bot commented Jun 7, 2026

Copy link
Copy Markdown

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

@github-actions github-actions Bot closed this Jun 7, 2026
@HodaSalim HodaSalim reopened this Jun 8, 2026
@HodaSalim HodaSalim marked this pull request as ready for review June 8, 2026 14:17
@HodaSalim HodaSalim requested a review from a team as a code owner June 8, 2026 14:17
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.

3 participants