noid-rails 3.0.2 → 3.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a9c5330c3c96082abb5e4a0ad3ec80c003ed246615214e8ea89c2208e61a5424
-  data.tar.gz: f3d00baafb689a67eda11864b2773f1234e4ba9e3260c357ecb6cc7cc314ea0f
+  metadata.gz: 2cbea20da5c324c2711c1870026241c59bfc873685b4e96696364e16fadd2a19
+  data.tar.gz: 887c02907ba46a5c7b9a9c349d61ad3afd4507b6b0c0cceb9118994b5f48286c
 SHA512:
-  metadata.gz: a4eab612b6608d12e31925fc168d60fcf264e1b483375c7d50e0a91a7822ba1a3cf84ce95367ee2b3e2ba58d1263112d2197c04b37b90bef1f922defa852c345
-  data.tar.gz: b4b0166a884902e1330380b7056e7e15a0f9cec50ff91f8fdbb0b829646965cb7ba63bb5010a4ed4e28f24afc0b9daa28c88a60099c4ae64f3a835b6e7f76cb8
+  metadata.gz: e5e4879180742e94910422d58283f90ede3c1bf726c361bbfaf02ceceb6bebfc95175e20d19530e751f73d60d5150d4eb5e7896d85bb40ddc7c77459f4b2fb0e
+  data.tar.gz: 91bfe3889556af3dd53e7fc18a94712fd49b060b69741ea0da03e0b84d9418becf2e9d1ba169ea0d793cedb6d7f98c3a06994f9a7bbdfd078d6cf64522323f5c

data/.circleci/config.yml

@@ -1,6 +1,6 @@
 version: 2.1
 orbs:
-  samvera: samvera/circleci-orb@0
+  samvera: samvera/circleci-orb@1.0
 jobs:
   bundle_and_test:
     parameters:
@@ -8,7 +8,7 @@ jobs:
         type: string
       bundler_version:
         type: string
-        default: 1.17.3
+        default: 2.4.3
       rails_version:
         type: string
     executor:
@@ -21,6 +21,19 @@ jobs:
     steps:
       - samvera/cached_checkout
 
+      - run:
+          name: Check for a branch named 'master'
+          command: |
+            git fetch --all --quiet --prune --prune-tags
+            if [[ -n "$(git branch --all --list master */master)" ]]; then
+              echo "A branch named 'master' was found. Please remove it."
+              echo "$(git branch --all --list master */master)"
+            fi
+            [[ -z "$(git branch --all --list master */master)" ]]
+
+      - run: 'sudo apt-get update'
+      - run: 'sudo apt-get install -y libsqlite3-dev'
+
       - samvera/bundle_for_gem:
           ruby_version: << parameters.ruby_version >>
           bundler_version: << parameters.bundler_version >>
@@ -42,49 +55,38 @@ workflows:
   ci:
     jobs:
       - bundle_and_test:
-          name: ruby2-7_rails6-0
-          ruby_version: 2.7.1
-          rails_version: 6.0.3.1
-      - bundle_and_test:
-          name: ruby2-7_rails5-2
-          ruby_version: 2.7.1
-          rails_version: 5.2.4.3
+          name: ruby3-2_rails7-0
+          ruby_version: 3.2.0
+          rails_version: 7.0.4
+
       - bundle_and_test:
-          name: ruby2-7_rails5-1
-          ruby_version: 2.7.1
-          rails_version: 5.1.7
+          name: ruby3-1_rails7-0
+          ruby_version: 3.1.3
+          rails_version: 7.0.4
 
       - bundle_and_test:
-          name: ruby2-6_rails6-0
-          ruby_version: 2.6.6
-          rails_version: 6.0.3.1
+          name: ruby3-0_rails7-0
+          ruby_version: 3.0.5
+          rails_version: 7.0.4
       - bundle_and_test:
-          name: ruby2-6_rails5-2
-          ruby_version: 2.6.6
-          rails_version: 5.2.4.3
+          name: ruby3-0_rails6-1
+          ruby_version: 3.0.5
+          rails_version: 6.1.7
       - bundle_and_test:
-          name: ruby2-6_rails5-1
-          ruby_version: 2.6.6
-          rails_version: 5.1.7
+          name: ruby3-0_rails6-0
+          ruby_version: 3.0.5
+          rails_version: 6.0.6
 
       - bundle_and_test:
-          name: ruby2-5_rails6-0
-          ruby_version: 2.5.8
-          rails_version: 6.0.3.1
+          name: ruby2-7_rails6-1
+          ruby_version: 2.7.7
+          rails_version: 6.1.7
       - bundle_and_test:
-          name: ruby2-5_rails5-2
-          ruby_version: 2.5.8
-          rails_version: 5.2.4.3
+          name: ruby2-7_rails6-0
+          ruby_version: 2.7.7
+          rails_version: 6.0.6
       - bundle_and_test:
-          name: ruby2-5_rails5-1
-          ruby_version: 2.5.8
-          rails_version: 5.1.7
+          name: ruby2-7_rails5-2
+          ruby_version: 2.7.7
+          rails_version: 5.2.8.1
 
-      - bundle_and_test:
-          name: ruby2-4_rails5-2
-          ruby_version: 2.4.10
-          rails_version: 5.2.4.3
-      - bundle_and_test:
-          name: ruby2-4_rails5-1
-          ruby_version: 2.4.10
-          rails_version: 5.1.7

data/.github_changelog_generator

@@ -1,2 +1,2 @@
 unreleased=true
-future-release=3.0.2
+future-release=3.0.3

data/CHANGELOG.md

@@ -1,8 +1,22 @@
 # Changelog
 
-## [3.0.2](https://github.com/samvera/noid-rails/tree/3.0.2) (2020-06-11)
+## [3.0.3](https://github.com/samvera/noid-rails/tree/3.0.3) (2021-05-13)
 
-[Full Changelog](https://github.com/samvera/noid-rails/compare/v3.0.1...3.0.2)
+[Full Changelog](https://github.com/samvera/noid-rails/compare/v3.0.2...3.0.3)
+
+**Merged pull requests:**
+
+- Fix code climate badge [\#102](https://github.com/samvera/noid-rails/pull/102) ([bess](https://github.com/bess))
+- Update CI matrix to only cover supported versions [\#101](https://github.com/samvera/noid-rails/pull/101) ([bess](https://github.com/bess))
+- Fix deprecated/removed update\_attributes! with update! [\#100](https://github.com/samvera/noid-rails/pull/100) ([dgcliff](https://github.com/dgcliff))
+- Remove remaining active\_fedora:noid references from README [\#99](https://github.com/samvera/noid-rails/pull/99) ([cjcolvar](https://github.com/cjcolvar))
+- Adding CONTRIBUTING.md
+
+This was uploaded via automation. [\#98](https://github.com/samvera/noid-rails/pull/98) ([jeremyf](https://github.com/jeremyf))
+
+## [v3.0.2](https://github.com/samvera/noid-rails/tree/v3.0.2) (2020-06-11)
+
+[Full Changelog](https://github.com/samvera/noid-rails/compare/v3.0.1...v3.0.2)
 
 **Implemented enhancements:**
 
@@ -16,6 +30,7 @@
 
 **Merged pull requests:**
 
+- Prep for 3.0.2 release [\#97](https://github.com/samvera/noid-rails/pull/97) ([bess](https://github.com/bess))
 - Align on current samvera style guide [\#96](https://github.com/samvera/noid-rails/pull/96) ([bess](https://github.com/bess))
 - Adding Ruby 2.7.z and Rails 6.y.z releases to the CircleCI build configuration [\#95](https://github.com/samvera/noid-rails/pull/95) ([jrgriffiniii](https://github.com/jrgriffiniii))
 - Update CircleCI Ruby and Rails versions [\#92](https://github.com/samvera/noid-rails/pull/92) ([botimer](https://github.com/botimer))
@@ -127,10 +142,6 @@
 
 [Full Changelog](https://github.com/samvera/noid-rails/compare/v2.0.0.beta6...v1.1.3)
 
-**Merged pull requests:**
-
-- Treeify algorithm should raise ArgumentError when passed nil or empty string [\#49](https://github.com/samvera/noid-rails/pull/49) ([mjgiarlo](https://github.com/mjgiarlo))
-
 ## [v2.0.0.beta6](https://github.com/samvera/noid-rails/tree/v2.0.0.beta6) (2016-10-26)
 
 [Full Changelog](https://github.com/samvera/noid-rails/compare/v2.0.0.beta5...v2.0.0.beta6)
@@ -177,6 +188,8 @@
 **Closed issues:**
 
 - Running generator raises an error. [\#37](https://github.com/samvera/noid-rails/issues/37)
+- Test gem in two configurations: with Rails and without Rails [\#36](https://github.com/samvera/noid-rails/issues/36)
+- Conditionalize autoload of Engine and classes that depend on ActiveRecord [\#35](https://github.com/samvera/noid-rails/issues/35)
 - MinterState isn't requirable by implementors. [\#29](https://github.com/samvera/noid-rails/issues/29)
 
 ## [v2.0.0.beta3](https://github.com/samvera/noid-rails/tree/v2.0.0.beta3) (2016-09-13)
@@ -225,7 +238,6 @@
 **Merged pull requests:**
 
 - Preserve the hash when translating to id. Fixes \#26 [\#27](https://github.com/samvera/noid-rails/pull/27) ([jcoyne](https://github.com/jcoyne))
-- Adding check for gone since that is also not a valid id to mint. [\#18](https://github.com/samvera/noid-rails/pull/18) ([carolyncole](https://github.com/carolyncole))
 
 ## [v1.1.0](https://github.com/samvera/noid-rails/tree/v1.1.0) (2016-05-10)
 
@@ -239,6 +251,10 @@
 
 [Full Changelog](https://github.com/samvera/noid-rails/compare/v1.0.2...v1.0.3)
 
+**Merged pull requests:**
+
+- Adding check for gone since that is also not a valid id to mint. [\#18](https://github.com/samvera/noid-rails/pull/18) ([carolyncole](https://github.com/carolyncole))
+
 ## [v1.0.2](https://github.com/samvera/noid-rails/tree/v1.0.2) (2015-08-11)
 
 [Full Changelog](https://github.com/samvera/noid-rails/compare/v1.0.1...v1.0.2)

data/CONTRIBUTING.md

@@ -22,6 +22,28 @@ https://wiki.duraspace.org/display/samvera/Samvera+Community+Intellectual+Proper
 
 You should also add yourself to the `CONTRIBUTORS.md` file in the root of the project.
 
+## Language
+
+The language we use matters.  Today, tomorrow, and for years to come
+people will read the code we write.  They will judge us for our
+design, logic, and the words we use to describe the system.
+
+Our words should be accessible.  Favor descriptive words that give
+meaning while avoiding reinforcing systemic inequities.  For example,
+in the Samvera community, we should favor using allowed\_list instead
+of whitelist, denied\_list instead of blacklist, or source/copy
+instead of master/slave.
+
+We're going to get it wrong, but this is a call to keep working to
+make it right.  View our code and the words we choose as a chance to
+have a conversation. A chance to grow an understanding of the systems
+we develop as well as the systems in which we live.
+
+See [“Blacklists” and “whitelists”: a salutary warning concerning the
+prevalence of racist language in discussions of predatory
+publishing](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6148600/) for
+further details.
+
 ## Contribution Tasks
 
 * Reporting Issues
@@ -34,7 +56,7 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
 ### Reporting Issues
 
 * Make sure you have a [GitHub account](https://github.com/signup/free)
-* Submit a [Github issue](https://github.com/samvera/noid-rails/issues) by:
+* Submit a [Github issue](https://github.com/samvera/noid-rails/issues/) by:
   * Clearly describing the issue
     * Provide a descriptive summary
     * Explain the expected behavior
@@ -45,15 +67,22 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
 
 * Fork the repository on GitHub
 * Create a topic branch from where you want to base your work.
-  * This is usually the master branch.
-  * To quickly create a topic branch based on master; `git branch fix/master/my_contribution master`
-  * Then checkout the new branch with `git checkout fix/master/my_contribution`.
-  * Please avoid working directly on the `master` branch.
+  * This is usually the `main` branch.
+  * To quickly create a topic branch based on `main`; `git branch fix/main/my_contribution main`
+  * Then checkout the new branch with `git checkout fix/main/my_contribution`.
+  * Please avoid working directly on the `main` branch.
+  * Please do not create a branch called `master`. (See note below.)
   * You may find the [hub suite of commands](https://github.com/defunkt/hub) helpful
 * Make sure you have added sufficient tests and documentation for your changes.
   * Test functionality with RSpec; Test features / UI with Capybara.
 * Run _all_ the tests to assure nothing else was accidentally broken.
 
+NOTE: This repository follows the [Samvera Community Code of Conduct](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Code+of+Conduct) 
+and [language recommendations](#language).  
+Please ***do not*** create a branch called `master` for this repository or as part of 
+your pull request; the branch will either need to be removed or renamed before it can 
+be considered for inclusion in the code base and history of this repository.
+
 ### Documenting Code
 
 * All new public methods, modules, and classes should include inline documentation in [YARD](http://yardoc.org/).
@@ -109,15 +138,15 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
 ### Submitting Changes
 
 * Read the article ["Using Pull Requests"](https://help.github.com/articles/using-pull-requests) on GitHub.
-* Make sure your branch is up to date with its parent branch (i.e. master)
-  * `git checkout master`
+* Make sure your branch is up to date with its parent branch (i.e. main)
+  * `git checkout main`
   * `git pull --rebase`
   * `git checkout <your-branch>`
-  * `git rebase master`
+  * `git rebase main`
   * It is a good idea to run your tests again.
 * If you've made more than one commit take a moment to consider whether squashing commits together would help improve their logical grouping.
   * [Detailed Walkthrough of One Pull Request per Commit](http://ndlib.github.io/practices/one-commit-per-pull-request/)
-  * `git rebase --interactive master` ([See Github help](https://help.github.com/articles/interactive-rebase))
+  * `git rebase --interactive main` ([See Github help](https://help.github.com/articles/interactive-rebase))
   * Squashing your branch's changes into one commit is "good form" and helps the person merging your request to see everything that is going on.
 * Push your changes to a topic branch in your fork of the repository.
 * Submit a pull request from your fork to the project.
@@ -127,12 +156,14 @@ You should also add yourself to the `CONTRIBUTORS.md` file in the root of the pr
 We adopted [Github's Pull Request Review](https://help.github.com/articles/about-pull-request-reviews/) for our repositories.
 Common checks that may occur in our repositories:
 
-1. Travis CI - where our automated tests are running
-2. Approval Required - Github enforces at least one person approve a pull request. Also, all reviewers that have chimed in must approve.
+1. [CircleCI](https://circleci.com/gh/samvera) - where our automated tests are running
+2. RuboCop/Bixby - where we check for style violations
+3. Approval Required - Github enforces at least one person approve a pull request. Also, all reviewers that have chimed in must approve.
+4. CodeClimate - is our code remaining healthy (at least according to static code analysis)
 
 If one or more of the required checks failed (or are incomplete), the code should not be merged (and the UI will not allow it). If all of the checks have passed, then anyone on the project (including the pull request submitter) may merge the code.
 
-*Example: Carolyn submits a pull request, Justin reviews the pull request and approves. However, Justin is still waiting on other checks (Travis CI is usually the culprit), so he does not merge the pull request. Eventually, all of the checks pass. At this point, Carolyn or anyone else may merge the pull request.*
+*Example: Carolyn submits a pull request, Justin reviews the pull request and approves. However, Justin is still waiting on other checks (CI tests are usually the culprit), so he does not merge the pull request. Eventually, all of the checks pass. At this point, Carolyn or anyone else may merge the pull request.*
 
 #### Things to Consider When Reviewing
 
@@ -149,7 +180,7 @@ This is your chance for a mentoring moment of another developer. Take time to gi
   * Do new or changed methods, modules, and classes have documentation?
   * Does the commit contain more than it should? Are two separate concerns being addressed in one commit?
   * Does the description of the new/changed specs match your understanding of what the spec is doing?
-  * Did the Travis tests complete successfully?
+  * Did the Continuous Integration tests complete successfully?
 
 If you are uncertain, bring other contributors into the conversation by assigning them as a reviewer.
 

data/README.md

@@ -1,10 +1,18 @@
 # Noid::Rails
 
-Code: [![Version](https://badge.fury.io/rb/noid-rails.png)](http://badge.fury.io/rb/noid-rails) [![Build Status](https://circleci.com/gh/samvera/noid-rails.svg?style=svg)](https://circleci.com/gh/samvera/noid-rails) [![Coverage Status](https://coveralls.io/repos/github/samvera/noid-rails/badge.svg?branch=master)](https://coveralls.io/github/samvera/noid-rails?branch=master) [![Code Climate](https://codeclimate.com/github/samvera/noid-rails/badges/gpa.svg)](https://codeclimate.com/github/samvera/noid-rails)
+Code:
+[![Gem Version](https://badge.fury.io/rb/noid-rails.png)](http://badge.fury.io/rb/noid-rails)
+[![Build Status](https://circleci.com/gh/samvera/noid-rails.svg?style=svg)](https://circleci.com/gh/samvera/noid-rails)
+[![Coverage Status](https://coveralls.io/repos/github/samvera/noid-rails/badge.svg?branch=main)](https://coveralls.io/github/samvera/noid-rails?branch=main)
+[![Maintainability](https://api.codeclimate.com/v1/badges/9c8739a529edc982fdec/maintainability)](https://codeclimate.com/github/samvera/noid-rails/maintainability)
 
-Docs: [![Apache 2.0 License](http://img.shields.io/badge/APACHE2-license-blue.svg)](./LICENSE) [![Contribution Guidelines](http://img.shields.io/badge/CONTRIBUTING-Guidelines-blue.svg)](./CONTRIBUTING.md) [![API Docs](http://img.shields.io/badge/API-docs-blue.svg)](http://rubydoc.info/gems/noid-rails) [![Documentation Status](https://inch-ci.org/github/samvera/noid-rails.svg?branch=master)](https://inch-ci.org/github/samvera/noid-rails)
+Docs:
+[![Contribution Guidelines](http://img.shields.io/badge/CONTRIBUTING-Guidelines-blue.svg)](./CONTRIBUTING.md)
+[![Apache 2.0 License](http://img.shields.io/badge/APACHE2-license-blue.svg)](./LICENSE)
+[![API Docs](http://img.shields.io/badge/API-docs-blue.svg)](http://rubydoc.info/gems/noid-rails)
+[![Documentation Status](https://inch-ci.org/github/samvera/noid-rails.svg?branch=main)](https://inch-ci.org/github/samvera/noid-rails)
 
-Jump In: [![Slack Status](http://slack.samvera.org/badge.svg)](http://slack.samvera.org/)
+Community Support: [![Samvera Community Slack](https://img.shields.io/badge/samvera-slack-blueviolet)](http://slack.samvera.org/)
 
 # What is noid-rails?
 
@@ -14,11 +22,13 @@ This gem mints identifiers for models in your Rails-based application with opaqu
 
 ## Product Owner & Maintenance
 
-**noid-rails** is a Core Component of the Samvera community. The documentation for what this means can be found [here](http://samvera.github.io/core_components.html#requirements-for-a-core-component).
+`noid-rails` was a Core Component of the Samvera Community. Given a decline in available labor required for maintenance, this project no longer has a dedicated Product Owner. The documentation for what this means can be found [here](http://samvera.github.io/core_components.html#requirements-for-a-core-component).
 
 ### Product Owner
 
-[Justin Coyne](https://github.com/jcoyne)
+**Vacant**
+
+_Until a Product Owner has been identified, we ask that you please direct all requests for support, bug reports, and general questions to the [`#dev` Channel on the Samvera Slack](https://samvera.slack.com/app_redirect?channel=dev)._
 
 ## Table of Contents
 
@@ -128,7 +138,7 @@ To better support multi-host production installations that expect a shared datab
 The database-based minter stores minter state information in your application's relational database. To use it, you'll first need to run the install generator:
 
 ```bash
-$ rails generate active_fedora:noid:install
+$ rails generate noid:rails:install
 ```
 
 This will create the necessary database migrations.
@@ -138,7 +148,7 @@ Then run `rake db:migrate`
 To start minting identifiers with the new minter, override the AF::Noid configuration in e.g. `config/initializers/noid-rails.rb`:
 
 ```ruby
-require 'active_fedora/noid'
+require 'noid-rails'
 
 Noid::Rails.configure do |config|
   config.minter_class = Noid::Rails::Minter::Db
@@ -148,7 +158,7 @@ end
 Using the database-backed minter can cause problems with your test suite, where it is often sensible to wipe out database rows between tests (which destroys the database-backed minter's state, which renders it unusable). To deal with this and still get the benefits of using the database-backed minter in development and production environments, you'll also want to add the following helper to your `spec/spec_helper.rb`:
 
 ```ruby
-require 'active_fedora/noid/rspec'
+require 'noid/rails/rspec'
 
 RSpec.configure do |config|
   include Noid::Rails::RSpec
@@ -219,6 +229,12 @@ end
 
 And the service will delegate minting and validating to an instance of your customized minter class.
 
+## Contributing 
+
+If you're working on PR for this project, create a feature branch off of `main`. 
+
+This repository follows the [Samvera Community Code of Conduct](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Code+of+Conduct) and [language recommendations](https://github.com/samvera/maintenance/blob/master/templates/CONTRIBUTING.md#language).  Please ***do not*** create a branch called `master` for this repository or as part of your pull request; the branch will either need to be removed or renamed before it can be considered for inclusion in the code base and history of this repository.
+
 ## Releasing
 
 1. `bundle install`
@@ -230,7 +246,7 @@ And the service will delegate minting and validating to an instance of your cust
   github_changelog_generator --user samvera --project noid-rails --token YOUR_GITHUB_TOKEN_HERE
   ```
 
-5. Commit these changes to the master branch
+5. Commit these changes to the main branch
 
 6. Run `rake release`
 

data/lib/noid/rails/minter/db.rb

@@ -35,7 +35,7 @@ module Noid
         # @param [::Noid::Minter] minter state containing the updates
         def serialize(inst, minter)
           # namespace and template are the same, now update the other attributes
-          inst.update_attributes!(
+          inst.update!(
             seq: minter.seq,
             counters: JSON.generate(minter.counters),
             rand: Marshal.dump(minter.instance_variable_get(:@rand))

data/lib/noid/rails/version.rb

@@ -2,6 +2,6 @@
 
 module Noid
   module Rails
-    VERSION = '3.0.2'
+    VERSION = '3.1.0'
   end
 end

data/noid-rails.gemspec

@@ -18,11 +18,11 @@ Gem::Specification.new do |spec|
   spec.test_files    = spec.files.grep(%r{^spec/})
   spec.require_paths = ['lib']
 
-  spec.add_dependency 'actionpack', '>= 5.0.0', '< 7'
+  spec.add_dependency 'actionpack', '>= 5.0.0', '< 7.1'
   spec.add_dependency 'noid', '~> 0.9'
 
-  spec.add_development_dependency 'bixby', '~> 3.0.0'
-  spec.add_development_dependency 'bundler', '>= 1.7'
+  spec.add_development_dependency 'bixby', '~> 5.0.0'
+  spec.add_development_dependency 'bundler', '>= 2.1'
   spec.add_development_dependency 'engine_cart', '~> 2.2'
   spec.add_development_dependency 'rake', '>= 11'
   spec.add_development_dependency 'rspec', '~> 3.8'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: noid-rails
 version: !ruby/object:Gem::Version
-  version: 3.0.2
+  version: 3.1.0
 platform: ruby
 authors:
 - Michael J. Giarlo
-autorequire:
+autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-06-11 00:00:00.000000000 Z
+date: 2023-01-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: actionpack
@@ -19,7 +19,7 @@ dependencies:
         version: 5.0.0
     - - "<"
       - !ruby/object:Gem::Version
-        version: '7'
+        version: '7.1'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -29,7 +29,7 @@ dependencies:
         version: 5.0.0
     - - "<"
       - !ruby/object:Gem::Version
-        version: '7'
+        version: '7.1'
 - !ruby/object:Gem::Dependency
   name: noid
   requirement: !ruby/object:Gem::Requirement
@@ -50,28 +50,28 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 3.0.0
+        version: 5.0.0
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 3.0.0
+        version: 5.0.0
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '1.7'
+        version: '2.1'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '1.7'
+        version: '2.1'
 - !ruby/object:Gem::Dependency
   name: engine_cart
   requirement: !ruby/object:Gem::Requirement
@@ -195,7 +195,7 @@ homepage: https://github.com/samvera/noid-rails
 licenses:
 - Apache2
 metadata: {}
-post_install_message:
+post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -210,8 +210,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.3
-signing_key:
+rubygems_version: 3.1.6
+signing_key: 
 specification_version: 4
 summary: Noid identifier services for Rails-based applications
 test_files: