migration-lock-timeout 1.4.0 → 2.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d977632b3898a8d9b0621fe5fd949baa78a34a7f80f5da64b0300137bbaa4e99
-  data.tar.gz: ac82abde1d14b82c587583d39f39d51f37590c722f97b33c84c6fe90fed884cf
+  metadata.gz: 23a039c3b5418a45787e521fb863cf3527bd02e8d158561ece67ae0043212172
+  data.tar.gz: 0b5d8d845b5c2afbbc444e7dd0ac37ce09b399483553005400b3e5208bb78af7
 SHA512:
-  metadata.gz: d70e023f19c3d74d49f4ac4458f7409b1742d68e93457d38173201a05e6e019b14b56fcb1288b9dbd9f3ef25ee93e2022aff4410bedf670e6e923e386d6e8e01
-  data.tar.gz: fc31edc45351ce308e961746883272197405ae0adbfa12bda2ed481d31b056220dab549e80f1f123f9f13b0420996edf3c173fd2f0c27f3d3363d2e4c8f92200
+  metadata.gz: 82a5a7418ded1b677ad089bd7b9b8cdbe9b783e84716c8f5da4dd5155e05dc7ea3e7780714f6367b03d3df8196eb82b15c66bdc0226fcbeac0ce0c08d069b344
+  data.tar.gz: 8555e3b5aaacc84503c2bd710415659f9dff1e7f75c8db2a895bae1195267cae72e96647aa0565f7e9c0b8d8294771ebf3eabb53802c6b95376a3e7ee0647386

data/.github/CODEOWNERS

@@ -0,0 +1 @@
+* @procore-oss/procore-migration-lock-timeout

data/.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,64 @@
+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)
+    value: |
+        - OS:
+        - Browser Name and 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 think 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 feature you'd like to see implemented
+    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,17 @@
+
+Checklist:
+
+* [ ] I have updated the necessary documentation
+* [ ] I have updated the changelog, if necessary (CHANGELOG.md)
+* [ ] I have signed off all my commits as required by [DCO](../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,7 @@
+version: 2
+updates:
+  - package-ecosystem: 'github-actions'
+    directory: '/'
+    schedule:
+      interval: 'weekly'
+      timezone: 'America/Chicago'

data/.github/labeler.yml

@@ -0,0 +1,9 @@
+repo:
+  - changed-files:
+      - any-glob-to-any-file:
+          - .github/**/*
+          - README.md
+          - .gitignore
+          - .gitattributes
+          - .gitmodules/**/*
+          - LICENSE

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

@@ -0,0 +1,15 @@
+name: "Auto Author Assign"
+on:
+  pull_request:
+    types: [opened, reopened, synchronize]
+
+permissions:
+  pull-requests: write
+
+jobs:
+  assign:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: toshimaru/auto-author-assign@4d585cc37690897bd9015942ed6e766aa7cdb97f # v3.0.1
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}

data/.github/workflows/codeql.yml

@@ -0,0 +1,35 @@
+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@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v4
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@cdefb33c0f6224e58673d9004f47f7cb3e328b89 # v3
+        with:
+          languages: ${{ matrix.language }}
+      - name: Autobuild
+        uses: github/codeql-action/autobuild@cdefb33c0f6224e58673d9004f47f7cb3e328b89 # v3
+      - name: Perform CodeQL Analysis
+        uses: github/codeql-action/analyze@cdefb33c0f6224e58673d9004f47f7cb3e328b89 # v3
+        with:
+          category: "/language:${{matrix.language}}"

data/.github/workflows/labeler.yml

@@ -0,0 +1,15 @@
+name: "Pull Request Labeler"
+on:
+  pull_request_target:
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  labeler:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/labeler@634933edcd8ababfe52f92936142cc22ac488b1b # v6.0.1
+        with:
+          repo-token: "${{ secrets.GITHUB_TOKEN }}"

data/.github/workflows/release.yml

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

data/.github/workflows/stale.yml

@@ -0,0 +1,40 @@
+name: "Close stale issues and PR"
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: "30 1 * * *" # https://crontab.guru/#30_1_*_*_* (everyday at 0130)
+
+permissions:
+  issues: write
+  pull-requests: write
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@997185467fa4f803885201cee163a9f38240193d # v10.1.1
+        with:
+          operations-per-run: 200
+          ascending: true
+          delete-branch: true
+          stale-issue-message: >
+            This issue is stale because it has been open 10 days with no activity.
+            Replace the `no-issue-activity` label with a `work-in-progress` label or comment or
+            this will be closed in 5 days.
+          close-issue-message: >
+            This issue was closed because it has been stalled for 5 days with no activity.
+          days-before-issue-stale: 10
+          days-before-issue-close: 5
+          stale-issue-label: "no-issue-activity"
+          exempt-issue-labels: "awaiting-approval,work-in-progress"
+          stale-pr-message: >
+            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.
+          close-pr-message: >
+            This PR was closed because it has been stalled for 5 days with no activity.
+          days-before-pr-stale: 20
+          days-before-pr-close: 5
+          stale-pr-label: "no-pr-activity"
+          exempt-pr-labels: "awaiting-approval,work-in-progress,dependencies"
+          exempt-pr-assignees: "snyk-github"

data/.github/workflows/test.yml

@@ -0,0 +1,46 @@
+name: Test
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+permissions:
+  contents: read
+jobs:
+  test:
+    strategy:
+      matrix:
+        os: [ubuntu-latest]
+        ruby: ['3.2', '3.3', '3.4']
+        postgres: ['15.1', '15.14']
+    runs-on: ${{ matrix.os }}
+    services:
+      postgres:
+        image: postgres:${{ matrix.postgres }}
+        env:
+          POSTGRES_PASSWORD: postgres
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd pg_isready
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+    env:
+      POSTGRES_DB_HOST: postgres
+      POSTGRES_DB_USERNAME: postgres
+      POSTGRES_DB_DATABASE: postgres
+      POSTGRES_DB_PASSWORD: postgres
+    steps:
+      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v4
+      - name: Set up Ruby ${{ matrix.ruby }}
+        uses: ruby/setup-ruby@675dd7ba1b06c8786a1480d89c384f5620a42647 # v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          bundler-cache: true
+      - name: Install Ruby Dependencies
+        run: bundle check || bundle install
+      - name: Install Appraisals Dependencies
+        run: bundle exec appraisal install
+      - name: Run Appraisals Tests
+        run: bundle exec appraisal rspec

data/.gitignore

@@ -1,6 +1,5 @@
 /.bundle/
 /.yardoc
-/Gemfile.lock
 /_yardoc/
 /coverage/
 /doc/
@@ -8,4 +7,3 @@
 /spec/reports/
 /tmp/
 *.gem
-/gemfiles/*.gemfile.lock

data/.ruby-version

@@ -1 +1 @@
-2.7.7
+3.1.6

data/Appraisals

@@ -1,41 +1,44 @@
-appraise "activerecord-4" do
-  gem "activerecord", "4.2.7.1"
-  gem "pg", "~> 0.21"
-  gem "bigdecimal", "1.3.5"
+appraise "activerecord_6_1" do
+  gem "activerecord", "~> 6.1.0"
 end
 
-appraise "activerecord-4_with_strong_migrations" do
-  gem "activerecord", "4.2.7.1"
+appraise "activerecord_6_1_with_strong_migrations" do
+  gem "activerecord", "~> 6.1.0"
   gem "strong_migrations", "0.2"
-  gem "pg", "~> 0.21"
-  gem "bigdecimal", "1.3.5"
 end
 
-appraise "activerecord-5" do
-  gem "activerecord", "5.0.0.1"
-  gem "pg", "~> 0.21"
+appraise "activerecord_7" do
+  gem "activerecord", "~> 7.0.1"
 end
 
-appraise "activerecord-5_with_strong_migrations" do
-  gem "activerecord", "5.0.0.1"
-  gem "strong_migrations", "0.2"
-  gem "pg", "~> 0.21"
+appraise "activerecord_7_with_strong_migrations" do
+  gem "activerecord", "~> 7.0.1"
+  gem "strong_migrations"
 end
 
-appraise "activerecord-6" do
-  gem "activerecord", "6.0.0"
+appraise "activerecord_7_1" do
+  gem "activerecord", "~> 7.1.0"
 end
 
-appraise "activerecord-6_with_strong_migrations" do
-  gem "activerecord", "6.0.0"
-  gem "strong_migrations", "0.2"
+appraise "activerecord_7_1_with_strong_migrations" do
+  gem "activerecord", "~> 7.1.0"
+  gem "strong_migrations"
+end
+
+appraise "activerecord_8_0" do
+  gem "activerecord", "~> 8.0.0"
+end
+
+appraise "activerecord_8_0_with_strong_migrations" do
+  gem "activerecord", "~> 8.0.0"
+  gem "strong_migrations"
 end
 
-appraise "activerecord-7" do
-  gem "activerecord", "7.0.0"
+appraise "activerecord_8_1" do
+  gem "activerecord", "~> 8.1.0"
 end
 
-appraise "activerecord-7_with_strong_migrations" do
-  gem "activerecord", "7.0.0"
+appraise "activerecord_8_1_with_strong_migrations" do
+  gem "activerecord", "~> 8.1.0"
   gem "strong_migrations"
 end

data/CHANGELOG.md

@@ -4,6 +4,19 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
 and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+
+## [2.0.0]
+### Removed
+- Dropped support for Ruby 3.1
+### Added
+- Support for Rails 8.0 and 8.1
+
+## [1.5.0]
+### Removed
+- Dropped support for Rails 6.0 and earlier
+- Dropped support for Ruby 3.0 and earlier
+
 ## [1.4.0]
 ### Added
 - Support for Rails 7

data/CODE_OF_CONDUCT.md

@@ -1,24 +1,41 @@
-# Contributor Code of Conduct
+# Contributor Covenant 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.
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, 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.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery
-* Personal attacks
-* Trolling or insulting/derogatory comments
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/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 electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
 
 Project maintainers have the right and responsibility to remove, edit, or
 reject comments, commits, code, wiki edits, issues, and other contributions
@@ -26,24 +43,34 @@ 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.
 
-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.
+## Scope
 
-This code of conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community.
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting a project maintainer at opensource@procore.com All
+## Enforcement
+
+Instances of abusive, harassing or otherwise unacceptable behavior may be
+reported by contacting the project team 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.
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality concerning the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
 
-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]
+[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
+<https://www.contributor-covenant.org/faq>

data/CONTRIBUTING.md

@@ -0,0 +1,23 @@
+# **Contributing**
+
+When contributing to this repository, please first discuss the change you wish to make via issue,
+email, or any other method with the owners of this repository before making a change.
+
+Please note we have a [code of conduct](CODE_OF_CONDUCT.md); please follow it in all your interactions with the project.
+
+## Pull Request Process
+
+1. Ensure any install or build dependencies are removed before the end of the layer when doing a
+   build.
+2. Update the README.md with details of changes to the interface; this includes new environment variables, exposed ports, valid file locations and container parameters.
+3. Increase the version numbers in any examples files and the README.md to the new version that this
+   Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
+4. You may merge the Pull Request once you have the sign-off of two other developers, or if you
+   do not have permission to do that, you may request the second reviewer to merge it for you.
+
+## Issue Report Process
+
+1. Go to the project's issues.
+2. Select the template that better fits your issue.
+3. Read the instructions carefully and write within the template guidelines.
+4. Submit it and wait for support.

data/Gemfile

@@ -1,4 +1,19 @@
+# frozen_string_literal: true
+
 source 'https://rubygems.org'
 
 # Specify your gem's dependencies in migration-lock-timeout.gemspec
 gemspec
+
+group :development, :test do
+  gem 'appraisal', require: false
+  gem 'base64', require: false
+  gem 'bigdecimal', require: false
+  gem 'benchmark', require: false
+  gem 'database_cleaner', require: false
+  gem 'pg', '~> 1.1', require: false
+  gem 'logger', require: false
+  gem 'mutex_m', require: false
+  gem 'rake', '~> 13', require: false
+  gem 'rspec', '~> 3.2', require: false
+end