handcuffs 1.4.0 → 2.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 91d9834315136aee1b7a94239c9f66ac9d0eb631
-  data.tar.gz: 1ca45f40052fba9fc009cfb1a0b28c9bf94d7405
+SHA256:
+  metadata.gz: dd48a0c4c4c2948afced7735d5f699648c000e5bbbcc3e4e795dff0f44f15c04
+  data.tar.gz: a6471b2358a4f1dae25251de3ae20665878e816e31a4f49687a6603673f69d82
 SHA512:
-  metadata.gz: 5e810600a0773709048bbad33a4d41254986fb380739efe3ddb7c81e60d2345052cdaf74a59bccead2a805c4bef1d3d9ed20de53ece2e738776e56d6c991f640
-  data.tar.gz: 833ad454a0d95dd2e8899d566e271645624cc065e492313ce279091fb377da5563564ae438f7e92c8e1f8ad5cca96b2d75b4428d38b8c28abdde2a375601cc88
+  metadata.gz: 873b8306a43cc09b1c524f1b4debdf4fd96bb47ab0ac8fd80a2b14287610b15ef596c13bc4ad65741507ec4a6be686f54763de0da84eefe7b28bcc14741a0be5
+  data.tar.gz: d1395678197fd1f74847970e3145002f67c535ac6beb8912b7c7a7990da80cebfee67bf29992f48f0383b834d2d991a5a7726e9c513280ffd81a5fc31a9a157f

data/.github/CODEOWNERS

@@ -0,0 +1 @@
+* @procore-oss/procore-ospo @procore-oss/procore-handcuffs

data/.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,66 @@
+name: 🐞 Bug
+description: File a bug/issue
+title: "[bug] <title>"
+labels: [bug, needs-triage]
+body:
+- type: checkboxes
+  attributes:
+    label: Is there an existing issue for this?
+    description: Please search to see if an issue already exists for the bug you encountered.
+    options:
+    - label: I have searched the existing issues
+      required: true
+- type: checkboxes
+  attributes:
+    label: Is this a regression?
+    description: Did this behavior work before?
+    options:
+    - label: Yes, this used to work before
+      required: false
+- type: textarea
+  attributes:
+    label: Current Behavior
+    description: A concise description of what you're experiencing.
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Expected Behavior
+    description: A concise description of what you expected to happen.
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Steps To Reproduce
+    description: Steps to reproduce the behavior.
+    placeholder: |
+      1.
+      2.
+      3.
+      4.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Environment
+    description: |
+      examples:
+        - **OS**: OSX 13.3.1
+        - **Browser Name and Version**: Chrome Version 112.0.5615.49 (Official Build) (arm64)
+        - **Ruby Version**: 3.0.0
+    value: |
+        - OS:
+        - Browser Name and version:
+        - Ruby Version:
+    render: markdown
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Anything else?
+    description: |
+      Links? References? Anything that will give us more context about the issue you are encountering!
+
+      Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+  validations:
+    required: false

data/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

data/.github/ISSUE_TEMPLATE/docs.yml

@@ -0,0 +1,18 @@
+name: 📚 Documentation or README.md issue report
+description: File a bug/issue for docs or README.md
+title: "[bug] <title>"
+labels: [docs, needs-triage]
+body:
+- type: checkboxes
+  attributes:
+    label: Is there an existing issue for this?
+    description: Please search to see if an issue already exists for the bug you encountered.
+    options:
+    - label: I have searched the existing issues
+      required: true
+- type: textarea
+  attributes:
+    label: Docs/README.md Part to update
+    description: A concise description of what you thing should be updated
+  validations:
+    required: true

data/.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,36 @@
+name: 🚀🆕 Feature Request
+description: Suggest an idea or possible new feature for this project
+title: "[Feature Request] <title>"
+labels: [feature, needs-triage]
+body:
+- type: checkboxes
+  attributes:
+    label: Is there an existing issue for this?
+    description: Please search to see if an issue already exists for the bug you encountered.
+    options:
+    - label: I have searched the existing issues
+      required: true
+- type: textarea
+  attributes:
+    label: Is your feature request related to a problem? Please describe
+    description: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Describe the solution you'd lik
+    description: A clear and concise description of what you want to happen
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Describe alternatives you've considered
+    description: A clear and concise description of any alternative solutions or features you've considered
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Additional context
+    description: Add any other context or additional information about the problem here
+  validations:
+    required: false

data/.github/ISSUE_TEMPLATE/question-support.yml

@@ -0,0 +1,18 @@
+name: ❓ Question or Support Request
+description: Questions and requests for support
+title: "[Question/Support] <title>"
+labels: [question, support, needs-triage]
+body:
+- type: checkboxes
+  attributes:
+    label: Is there an existing issue for this?
+    description: Please search to see if an issue already exists for the bug you encountered.
+    options:
+    - label: I have searched the existing issues
+      required: true
+- type: textarea
+  attributes:
+    label: Describe your question or ask for support
+    description: A concise description of what you would like support with
+  validations:
+    required: true

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,15 @@
+Checklist:
+
+* [ ] I have updated the necessary documentation
+* [ ] I have signed off all my commits as required by [DCO](https://github.com/procore-oss/handcuffs/blob/main/CONTRIBUTING.md)
+* [ ] My build is green
+
+<!--
+Note on DCO:
+
+If the DCO check fails, one or more of your commits are not signed off. Please click on the *Details* link next to the DCO action for instructions on how to resolve this.
+
+Note on Versioning:
+
+Maintainers will bump the version and do a release when they are ready to release (possibly multiple merged PRs). Please do not bump the version in your PRs.
+-->

data/.github/dependabot.yaml

@@ -0,0 +1,20 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: /
+    schedule:
+      interval: "weekly"
+      timezone: "America/Los_Angeles"
+    labels:
+      - "dependabot"
+      - "dependencies"
+      - "github-actions"
+  - package-ecosystem: "bundler"
+    directory: /
+    schedule:
+      interval: "weekly"
+      timezone: "America/Los_Angeles"
+    labels:
+      - "dependabot"
+      - "dependencies"
+      - "bundler"

data/.github/workflows/auto-assign-author.yaml

@@ -0,0 +1,13 @@
+name: 'Auto Author Assign'
+
+on:
+  pull_request_target:
+    types: [opened, reopened]
+
+jobs:
+  assign-author:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: toshimaru/auto-author-assign@v2.1.0
+        with:
+          repo-token: "${{ secrets.GITHUB_TOKEN }}"

data/.github/workflows/codeql.yaml

@@ -0,0 +1,43 @@
+name: "Custom CodeQL"
+
+on:
+  workflow_dispatch:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+
+permissions:
+  contents: read
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: Ubuntu-latest
+    timeout-minutes: ${{ (matrix.language == 'swift' && 120) || 360 }}
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [ 'ruby' ]
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v3
+      with:
+        languages: ${{ matrix.language }}
+
+    - name: Autobuild
+      uses: github/codeql-action/autobuild@v3
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v3
+      with:
+        category: "/language:${{matrix.language}}"

data/.github/workflows/release.yaml

@@ -0,0 +1,40 @@
+name: Release
+on:
+  workflow_run:
+    workflows: [Test]
+    types: [completed]
+    branches: [main]
+  workflow_dispatch: # allow manual deployment through GitHub Action UI
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    if: ${{ github.event_name == 'workflow_dispatch' || github.event.workflow_run.conclusion == 'success' }}
+    steps:
+      - uses: actions/checkout@v4
+      - name: Version file changed
+        id: version-file-changed
+        uses: tj-actions/changed-files@v42
+        with:
+          files: lib/handcuffs/version.rb
+      - name: Set up Ruby
+        if: ${{ github.event_name == 'workflow_dispatch' || steps.version-file-changed.outputs.any_changed == 'true' }}
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 3.2
+          bundler-cache: true
+      - name: Installing dependencies
+        if: ${{ github.event_name == 'workflow_dispatch' || steps.version-file-changed.outputs.any_changed == 'true' }}
+        run: bundle check --path=vendor/bundle || bundle install --path=vendor/bundle
+      - name: Build gem file
+        if: ${{ github.event_name == 'workflow_dispatch' || steps.version-file-changed.outputs.any_changed == 'true' }}
+        run: bundle exec rake build
+      - uses: fac/ruby-gem-setup-credentials-action@v2
+        if: ${{ github.event_name == 'workflow_dispatch' || steps.version-file-changed.outputs.any_changed == 'true' }}
+        with:
+          user: ""
+          key: rubygems
+          token: ${{secrets.RUBY_GEMS_API_KEY}}
+      - uses: fac/ruby-gem-push-action@v2
+        if: ${{ github.event_name == 'workflow_dispatch' || steps.version-file-changed.outputs.any_changed == 'true' }}
+        with:
+          key: rubygems

data/.github/workflows/stale.yaml

@@ -0,0 +1,38 @@
+## Reference: https://github.com/actions/stale
+name: Mark stale issues and pull requests
+on:
+  schedule:
+  - cron: "30 1 * * *"
+
+permissions:
+  contents: read
+
+jobs:
+  stale:
+    permissions:
+      issues: write  # for actions/stale to close stale issues
+      pull-requests: write  # for actions/stale to close stale PRs
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/stale@v9
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        # Number of days of inactivity before an issue becomes stale
+        days-before-stale: 60
+        # Number of days of inactivity before a stale issue is closed
+        days-before-close: 7
+        # Issues with these labels will never be considered stale
+        exempt-issue-labels: "on-hold,pinned,security"
+        exempt-pr-labels: "on-hold,pinned,security"
+        # Comment to post when marking an issue as stale.
+        stale-issue-message: >
+          This issue has been automatically marked as stale because it has not had
+          recent activity. It will be closed if no further activity occurs. Thank you
+          for your contributions.
+        stale-pr-message: >
+          This pull request has been automatically marked as stale because it has not had
+          recent activity. It will be closed if no further activity occurs. Thank you
+          for your contributions.
+        # Label to use when marking an issue as stale
+        stale-issue-label: 'no-issue-activity'
+        stale-pr-label: 'no-pr-activity'

data/.github/workflows/test.yaml

@@ -0,0 +1,54 @@
+name: Test
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+permissions:
+  contents: read
+jobs:
+  test:
+    strategy:
+      matrix:
+        ruby: ['2.7', '3.0', '3.1', '3.2', '3.3']
+        postgres: ['16-bullseye', '15-bullseye', '14-bullseye', '13-bullseye', '12-bullseye']
+    name: Ruby ${{ matrix.ruby }} - PostgreSQL ${{ matrix.postgres }}
+    # https://docs.github.com/en/actions/learn-github-actions/expressions#example
+    runs-on: ${{ matrix.ruby == '2.7' && 'ubuntu-20.04' || 'ubuntu-latest' }}
+    services:
+      postgres:
+        image: postgres:${{ matrix.postgres }}
+        env:
+          POSTGRES_USER: ubuntu
+          POSTGRES_DB: handcuffs_test
+          POSTGRES_HOST_AUTH_METHOD: trust
+        options: >-
+          --health-cmd pg_isready
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+        ports:
+          - 5432:5432
+    env:
+      PGHOST: localhost
+      PGUSER: ubuntu
+      RAILS_ENV: test
+      BUNDLER_VERSION: 2.4.22
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up Ruby ${{ matrix.ruby }}
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          bundler: ${{ env.BUNDLER_VERSION }}
+          bundler-cache: true
+      - name: Installing dependencies
+        run: bundle install && cd spec/dummy && bundle install
+      - name: Install Apprasals Dependencies
+        run: bundle exec appraisal install && cd spec/dummy && bundle exec appraisal install
+      - name: Setup Database
+        run: cd spec/dummy && bundle exec rake db:create db:migrate --trace
+      - name: Run Appraisals Tests
+        run: bundle exec appraisal rspec
+      - name: Run Dummy App Tests
+        run: cd spec/dummy && bundle exec appraisal bin/rspec

data/.gitignore

@@ -1,6 +1,7 @@
 /.bundle/
 /.yardoc
 /Gemfile.lock
+/gemfiles/*.gemfile.lock
 /_yardoc/
 /coverage/
 /doc/
@@ -8,5 +9,5 @@
 /spec/reports/
 /tmp/
 handcuffs-*.gem
-/gemfiles/*.gemfile.lock
 .ruby-version
+.DS_Store

data/Appraisals

@@ -1,28 +1,11 @@
-# Ruby 2.7 doesn't support BigDecimal.new, which Rails 4 uses
-if RUBY_VERSION < "2.7"
-  appraise "rails-4" do
-    gem "rails", "~> 4.2.8"
-    gem 'pg', '~> 0.15'
-  end
+appraise "rails-6.1" do
+  gem "rails", "~> 6.1.0"
 end
 
-appraise "rails-5" do
-  gem "rails", "~> 5.0.0.1"
-  gem 'pg', '~> 0.18'
+appraise "rails-7.0" do
+  gem "rails", "~> 7.0.0"
 end
 
-appraise "rails-5.1" do
-  gem "rails", "~> 5.1.7"
-  gem 'pg', '~> 0.18'
-end
-
-appraise "rails-5.2" do
-  gem "rails", "~> 5.2.3"
-end
-
-# Rails >= 6 requires Ruby >= 2.5
-if RUBY_VERSION >= "2.5"
-  appraise "rails-6" do
-    gem "rails", "~> 6.0.1"
-  end
+appraise "rails-7.1" do
+  gem "rails", "~> 7.1.0"
 end

data/CHANGELOG.md

@@ -0,0 +1,30 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## 2.0.0
+
+### Added
+
+- CHANGELOG.md
+- Code coverage for specs
+
+### Changed
+
+- Switched to new `cimg` docker imaged for CircleCI testing.
+- Switched to matrix testing for
+  - PostgreSQL 12, 13, 14, 15, 16;
+  - Ruby 2.7, 3.0, 3.1, 3.2, 3.3;
+  - Rails 6.1, 7.0, 7.1 (via Appraisal).
+- Updated Bundler to 2.4.22.
+- Added Appraisal for dummy app testing.
+- Moved repo to procore-oss
+
+### Removed
+
+- BREAKING CHANGE: Removed support for Ruby < 2.7, Rails < 6.1, PostgreSQL < 12.

data/CODE_OF_CONDUCT.md

@@ -1,49 +1,130 @@
-# Contributor Code of Conduct
+# Code of Conduct
 
-As contributors and maintainers of this project, and in the interest of
-fostering an open and welcoming community, we pledge to respect all people who
-contribute through reporting issues, posting feature requests, updating
-documentation, submitting pull requests or patches, and other activities.
+## Our Pledge
 
-We are committed to making participation in this project a harassment-free
-experience for everyone, regardless of level of experience, gender, gender
-identity and expression, sexual orientation, disability, personal appearance,
-body size, race, ethnicity, age, religion, or nationality.
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
 
-Examples of unacceptable behavior by participants include:
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
 
-* The use of sexualized language or imagery
-* Personal attacks
-* Trolling or insulting/derogatory comments
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
 * Public or private harassment
-* Publishing other's private information, such as physical or electronic
-  addresses, without explicit permission
-* Other unethical or unprofessional conduct
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Spam or other deceptive practices that take advantage of the community
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
 
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+## Scope
 
-By adopting this Code of Conduct, project maintainers commit themselves to
-fairly and consistently applying these principles to every aspect of managing
-this project. Project maintainers who do not follow or enforce the Code of
-Conduct may be permanently removed from the project team.
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
 
-This code of conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community.
+## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting a project maintainer at opensource@procore.com All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. Maintainers are
-obligated to maintain confidentiality with regard to the reporter of an
-incident.
+reported to the community leaders responsible for enforcement at
+<opensource@procore.com>.
+All complaints will be reviewed and investigated promptly and fairly by
+the Procore Open Source Program Office (OSPO)
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 1.3.0, available at
-[http://contributor-covenant.org/version/1/3/0/][version]
+version 2.0, available at
+<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
 
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/3/0/
+For answers to common questions about this code of conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are available at
+<https://www.contributor-covenant.org/translations>.

data/CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# Contributing to Procore Projects
+
+This document explains the common procedures expected by contributors while submitting code to Procore open source projects.
+
+## Code of Conduct
+
+Please read and abide by the [Code of Conduct](CODE_OF_CONDUCT.md)
+
+## General workflow
+
+Once a GitHub issue is accepted and assigned to you, please follow general workflow in order to submit your contribution:
+
+1. Fork the target repository under your GitHub username.
+2. Create a branch in your forked repository for the changes you are about to make.
+3. Commit your changes in the branch you created in step 2. All commits need to be signed-off. Check the [legal](#legal) section bellow for more details.
+4. Push your commits to your remote fork.
+5. Create a Pull Request from your remote fork pointing to the HEAD branch (usually `main` branch) of the target repository.
+6. Check the GitHub build and ensure that all checks are green.
+
+## Legal
+
+Procore projects use Developer Certificate of Origin ([DCO](https://GitHub.com/apps/dco/)).
+
+Please sign-off your contributions by doing ONE of the following:
+
+* Use `git commit -s ...` with each commit to add the sign-off or
+* Manually add a `Signed-off-by: Your Name <your.email@example.com>` to each commit message.
+
+The email address must match your primary GitHub email. You do NOT need cryptographic (e.g. gpg) signing.
+
+* Use `git commit -s --amend ...` to add a sign-off to the latest commit, if you forgot.
+
+*Note*: Some projects will provide specific configuration to ensure all commits are signed-off. Please check the project's documentation for more details.
+
+## Tests
+
+Make sure your changes are properly covered by automated tests. We aim to build an efficient test suite that is low cost to maintain and bring value to project. Prefer writing unit-tests over heavy end-to-end (e2e) tests. However, sometimes e2e tests are necessary. If you aren't sure, ask one of the maintainers about the requirements for your pull-request.

data/README.md

@@ -1,9 +1,10 @@
 # Handcuffs
 
-[![Circle CI](https://circleci.com/gh/procore/handcuffs.svg?style=svg)](https://circleci.com/gh/procore/handcuffs)
+[![Test](https://github.com/procore-oss/handcuffs/actions/workflows/test.yaml/badge.svg?branch=main)](https://github.com/procore-oss/handcuffs/actions/workflows/test.yaml)
+[![Gem Version](https://badge.fury.io/rb/handcuffs.svg)](https://badge.fury.io/rb/handcuffs)
+[![Discord](https://img.shields.io/badge/Chat-EDEDED?logo=discord)](https://discord.gg/PbntEMmWws) 
 
-Handcuffs provides an easy way to run migrations in phases in your [Ruby on
-Rails](https://rubyonrails.org/) application.
+Handcuffs provides an easy way to run migrations in phases in your [Ruby on Rails](https://rubyonrails.org/) application.
 
 To configure, first create a handcuff initializer and define a configuration
 
@@ -54,25 +55,27 @@ end
 ```
 
 You can then run your migrations in phases using
+
 ```bash
 rake 'handcuffs:migrate[pre_restart]'
 ```
+
 or
+
 ```bash
 rake 'handcuffs:migrate[post_restart]'
 ```
 
 You can run all migrations using
+
 ```bash
 rake 'handcuffs:migrate[all]'
 ```
 
-This differs from running `rake db:migrate` in that migrations will be run in
-the _order that the phases are defined in the handcuffs config_.
+This differs from running `rake db:migrate` in that migrations will be run in the _order that the phases are defined in the handcuffs config_.
+
+If you run a handcuffs rake task and any migration does not have a phase defined, an error will be raised before any migrations are run. To prevent this error, you can define a default phase for migrations that don't define one.
 
-If you run a handcuffs rake task and any migration does not have a phase
-defined, an error will be raised before any migrations are run. To prevent this
-error, you can define a default phase for migrations that don't define one.
 ```ruby
 # config/initializers/handcuffs.rb
 
@@ -92,23 +95,23 @@ gem 'handcuffs'
 
 And then execute:
 
-    $ bundle
+```bash
+bundle
+```
 
 Or install it yourself as:
 
-    $ gem install handcuffs
+```bash
+gem install handcuffs
+```
 
 ## Running specs
 
-The specs for handcuffs are in the dummy application at `/spec/dummy/spec`. The
-spec suite requires PostgreSQL. To run it you will have to set the environment
-variables `POSTGRES_DB_USERNAME` and `POSTGRES_DB_PASSWORD`. You can then run
-the suite using `rake spec`
+The specs for handcuffs are in the dummy application at `/spec/dummy/spec`. The spec suite requires PostgreSQL. To run it you will have to set the environment variables `POSTGRES_DB_USERNAME` and `POSTGRES_DB_PASSWORD`. You can then run the suite using `rake spec`
 
 ## Contributing
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/procore/handcuffs. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
-
+Bug reports and pull requests are welcome on GitHub at <https://github.com/procore-oss/handcuffs>. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
 
 ## License
 

data/SECURITY.md

@@ -0,0 +1,19 @@
+# Security Policy
+
+## Supported Versions
+
+Ruby versions that are currently being supported with security updates.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| <=2.6   | :x:                |
+| 2.7     | :white_check_mark: |
+| 3.0     | :white_check_mark: |
+| 3.1     | :white_check_mark: |
+| 3.2     | :white_check_mark: |
+
+## Reporting a Vulnerability
+
+Please click the `Report a vulnerability` button [here](https://github.com/procore-oss/handcuffs/security) to report a vulnerability.
+
+A maintainer will respond to you as soon as possible and discuss the process to get the vulnerability fixed.

data/gemfiles/{rails_5.2.gemfile → rails_6.1.gemfile}

@@ -2,6 +2,6 @@
 
 source "https://rubygems.org"
 
-gem "rails", "~> 5.2.3"
+gem "rails", "~> 6.1.0"
 
 gemspec path: "../"

data/gemfiles/{rails_6.gemfile → rails_7.0.gemfile}

@@ -2,6 +2,6 @@
 
 source "https://rubygems.org"
 
-gem "rails", "~> 6.0.1"
+gem "rails", "~> 7.0.0"
 
 gemspec path: "../"

data/gemfiles/{rails_4.gemfile → rails_7.1.gemfile}

@@ -2,7 +2,6 @@
 
 source "https://rubygems.org"
 
-gem "rails", "~> 4.2.8"
-gem "pg", "~> 0.15"
+gem "rails", "~> 7.1.0"
 
 gemspec path: "../"

data/handcuffs.gemspec

@@ -6,18 +6,20 @@ require 'handcuffs/version'
 Gem::Specification.new do |spec|
   spec.name          = "handcuffs"
   spec.version       = Handcuffs::VERSION
-  spec.authors       = ["Brad Urani"]
-  spec.email         = ["bradurani@gmail.com", "opensource@procore.com"]
+  spec.authors       = ["Procore Technologies, Inc."]
+  spec.email         = ["opensource@procore.com"]
 
   spec.summary       = %q{A Ruby gem for running Active Record migrations in phases}
   spec.description   = %q{Allows you to define a phase on Active Record migrations and provides rake tasks for running only migrations tagged with a certain phase}
-  spec.homepage      = "https://github.com/procore/handcuffs/"
+  spec.homepage      = "https://github.com/procore-oss/handcuffs/"
   spec.license       = "MIT"
 
   # Prevent pushing this gem to RubyGems.org by setting 'allowed_push_host', or
   # delete this section to allow pushing this gem to any host.
   if spec.respond_to?(:metadata)
     spec.metadata['allowed_push_host'] = "https://rubygems.org"
+    spec.metadata['rubygems_mfa_required'] = 'true'
+    spec.metadata['homepage_uri'] = spec.homepage
   else
     raise "RubyGems 2.0 or newer is required to protect against public gem pushes."
   end
@@ -32,6 +34,7 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency "pry"
   spec.add_development_dependency "pry-byebug"
   spec.add_development_dependency "rspec-rails", "~> 3.0"
+  spec.add_development_dependency "simplecov"
 
-  spec.add_runtime_dependency "rails", ">= 4.0", "< 6.1"
+  spec.add_runtime_dependency "rails", ">= 6.1"
 end

data/lib/handcuffs/errors.rb

@@ -44,7 +44,7 @@
   class HandcuffsPhaseOutOfOrderError < HandcuffsError
     def initialize(not_run_phase, attempted_phase)
       msg = <<-MESSAGE
-        Your tried to run #{attempted_phase.to_s}, but #{not_run_phase.to_s} has not been run
+        You tried to run #{attempted_phase.to_s}, but #{not_run_phase.to_s} has not been run
       MESSAGE
       super msg
     end

data/lib/handcuffs/version.rb

@@ -1,3 +1,3 @@
 module Handcuffs
-  VERSION = "1.4.0"
+  VERSION = "2.0.0"
 end

data/lib/tasks/handcuffs.rake

@@ -47,7 +47,7 @@ namespace :handcuffs do
         runnable.find_all { |m| ran?(m) }
       end
     end
- end
+  end
 
   module PhaseAccessor
     attr_accessor :handcuffs_phase

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: handcuffs
 version: !ruby/object:Gem::Version
-  version: 1.4.0
+  version: 2.0.0
 platform: ruby
 authors:
-- Brad Urani
+- Procore Technologies, Inc.
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2020-02-24 00:00:00.000000000 Z
+date: 2024-02-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: appraisal
@@ -81,13 +81,24 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '3.0'
 - !ruby/object:Gem::Dependency
-  name: rails
+  name: simplecov
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '4.0'
-    - - "<"
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rails
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
       - !ruby/object:Gem::Version
         version: '6.1'
   type: :runtime
@@ -95,36 +106,45 @@ dependencies:
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
-      - !ruby/object:Gem::Version
-        version: '4.0'
-    - - "<"
       - !ruby/object:Gem::Version
         version: '6.1'
 description: Allows you to define a phase on Active Record migrations and provides
   rake tasks for running only migrations tagged with a certain phase
 email:
-- bradurani@gmail.com
 - opensource@procore.com
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".circleci/config.yml"
+- ".github/CODEOWNERS"
+- ".github/ISSUE_TEMPLATE/bug.yml"
+- ".github/ISSUE_TEMPLATE/config.yml"
+- ".github/ISSUE_TEMPLATE/docs.yml"
+- ".github/ISSUE_TEMPLATE/feature-request.yml"
+- ".github/ISSUE_TEMPLATE/question-support.yml"
+- ".github/PULL_REQUEST_TEMPLATE.md"
+- ".github/dependabot.yaml"
+- ".github/workflows/auto-assign-author.yaml"
+- ".github/workflows/codeql.yaml"
+- ".github/workflows/release.yaml"
+- ".github/workflows/stale.yaml"
+- ".github/workflows/test.yaml"
 - ".gitignore"
 - Appraisals
+- CHANGELOG.md
 - CODE_OF_CONDUCT.md
+- CONTRIBUTING.md
 - Gemfile
-- LICENSE.txt
+- LICENSE.md
 - README.md
 - Rakefile
+- SECURITY.md
 - bin/console
 - bin/setup
 - gemfiles/.bundle/config
-- gemfiles/rails_4.gemfile
-- gemfiles/rails_5.1.gemfile
-- gemfiles/rails_5.2.gemfile
-- gemfiles/rails_5.gemfile
-- gemfiles/rails_6.gemfile
+- gemfiles/rails_6.1.gemfile
+- gemfiles/rails_7.0.gemfile
+- gemfiles/rails_7.1.gemfile
 - handcuffs.gemspec
 - lib/handcuffs.rb
 - lib/handcuffs/configuration.rb
@@ -136,11 +156,13 @@ files:
 - lib/handcuffs/railtie.rb
 - lib/handcuffs/version.rb
 - lib/tasks/handcuffs.rake
-homepage: https://github.com/procore/handcuffs/
+homepage: https://github.com/procore-oss/handcuffs/
 licenses:
 - MIT
 metadata:
   allowed_push_host: https://rubygems.org
+  rubygems_mfa_required: 'true'
+  homepage_uri: https://github.com/procore-oss/handcuffs/
 post_install_message: 
 rdoc_options: []
 require_paths:
@@ -156,8 +178,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.6.11
+rubygems_version: 3.4.19
 signing_key: 
 specification_version: 4
 summary: A Ruby gem for running Active Record migrations in phases

data/.circleci/config.yml

@@ -1,98 +0,0 @@
-version: 2
-
-aliases:
-  database: &database
-    image: circleci/postgres:10-ram
-    environment:
-      POSTGRES_USER: ubuntu
-      POSTGRES_DB: handcuffs_test
-      POSTGRES_HOST_AUTH_METHOD: trust
-
-  test_env: &test_env
-    - PGHOST=localhost
-    - PGUSER=ubuntu
-    - RAILS_ENV=test
-    - BUNDLER_VERSION=1.17.3
-
-  run_tests: &run_tests
-    - checkout
-
-    - run:
-        name: Install Bundler
-        command: gem install bundler:1.17.3
-
-    - run:
-        name: Install Ruby Dependencies
-        command: bundle install && cd spec/dummy && bundle install
-
-    - run:
-        name: Install Apprasals Dependencies
-        command: bundle exec appraisal install
-
-    - run:
-        name: Setup Database
-        command: cd spec/dummy && bundle exec rake db:create db:migrate --trace
-
-    - run:
-        name: Run Appraisals Tests
-        command: bundle exec appraisal rspec
-
-    - run:
-        name: Run Dummy App Tests
-        command: cd spec/dummy && bin/rspec
-
-jobs:
-  ruby_2_3:
-    docker:
-      - image: circleci/ruby:2.3
-        environment:
-          *test_env
-      - *database
-    steps:
-      *run_tests
-
-  ruby_2_4:
-    docker:
-      - image: circleci/ruby:2.4
-        environment:
-          *test_env
-      - *database
-    steps:
-      *run_tests
-
-  ruby_2_5:
-    docker:
-      - image: circleci/ruby:2.5
-        environment:
-          *test_env
-      - *database
-    steps:
-      *run_tests
-
-  ruby_2_6:
-    docker:
-      - image: circleci/ruby:2.6
-        environment:
-          *test_env
-      - *database
-    steps:
-      *run_tests
-
-  ruby_2_7:
-    docker:
-      - image: circleci/ruby:2.7
-        environment:
-          *test_env
-      - *database
-    steps:
-      *run_tests
-
-workflows:
-  version: 2
-  test-all:
-    jobs:
-      - ruby_2_3
-      - ruby_2_4
-      - ruby_2_5
-      - ruby_2_6
-      - ruby_2_7

data/gemfiles/rails_5.1.gemfile

@@ -1,8 +0,0 @@
-# This file was generated by Appraisal
-
-source "https://rubygems.org"
-
-gem "rails", "~> 5.1.7"
-gem "pg", "~> 0.18"
-
-gemspec path: "../"

data/gemfiles/rails_5.gemfile

@@ -1,8 +0,0 @@
-# This file was generated by Appraisal
-
-source "https://rubygems.org"
-
-gem "rails", "~> 5.0.0.1"
-gem "pg", "~> 0.18"
-
-gemspec path: "../"