archival_record 4.0.0 → 4.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c315fb06fde509b19bfc47160a1f2d4a6ecfe7366f3d1282a79617ec52cd43a7
-  data.tar.gz: bec372e44222e0ca89c599a2394de54e4ae6487235efb07487f6069bf9896ea1
+  metadata.gz: a75201e40595114329b5ecf7f2e790a37c57a94640755fc50fc2d330f2065056
+  data.tar.gz: 7fa088f8c71f94aa613807d0f493178db771b993c41f1a0b266665940137eea9
 SHA512:
-  metadata.gz: ca80d2342eb66c07303c24260f9d09d8b6f2f2b6dff8f5a5f43e21e3cdf0a7d1dc3a149db270a23fb8ca51383d67323e9ef60ff4f1877a38ddb7e8859329ef7c
-  data.tar.gz: f40ccfc73c58ec33159f1cb0a400145f1f23c928f86623317841e09cf3220fe3ac4127a09d6d915fd9d7d3c98b0c8b5279131c0918c476293bd4f16ff1a7c9b9
+  metadata.gz: e5b6fb27d71b390549bbbcb50de73c000432521083f662e1f77ffdea2904b6782df8f54cc54a088946a6aacd4cf104e5c9d531e9a5d88851aca954ab74f5062c
+  data.tar.gz: d0daae3db6a6841c4185c0be8d25e0459df61f21b3d41c0f898cb18b06bcc9ac4a9d6867ee0f73c4246b08850aca8bad095df3ef05f5b8bf54ec33e4e2d3b836

data/.rubocop.yml

@@ -1,4 +1,3 @@
-inherit_from: .rubocop_todo.yml
 plugins:
   - rubocop-rails
   - rubocop-rake
@@ -54,7 +53,7 @@ Style/AsciiComments:
 
 # TODO: class documentation
 Style/Documentation:
-  Enabled: false
+  Enabled: true
 
 Style/DoubleNegation:
   Enabled: false

data/CHANGELOG.md

@@ -1,5 +1,8 @@
 # CHANGELOG
 
+## 4.0.1 - March 25, 2025
+* Fixing links on rubygems.org to point to codeberg since that config move to [metadata](https://guides.rubygems.org/specification-reference/#metadata) in the past couple years
+
 ## 4.0.0 - March 19, 2025
 * **BREAKING CHANGE** `unarchive` behavior changed if you had non-`dependent: :destroy` `has_many` relationship but equal archive numbers on archived records before, the associated record would be unarchived. Now it won't. *You probably weren't doing this. If you were, why? How did you find out you could? Did you intend to? Anyway I broke it for you if you did find this extremely odd edge case. Sorry.* see: https://codeberg.org/joelmeador/archival_record/commit/19e02708f5ec97aa9b56a51cb7a84283e73e65aa
 * **BREAKING CHANGE** `archive` and `unarchive` now will act on `has_many` relations that are marked as `dependent: :delete_all` and `dependent: :destroy_async` in addition to `dependent: :destroy`. see: https://codeberg.org/joelmeador/archival_record/commit/685d7c6abb123422f2f8665252b99423dada305a

data/Gemfile.lock

@@ -33,7 +33,7 @@ GEM
       bundler
       rake
       thor (>= 0.14.0)
-    ast (2.4.2)
+    ast (2.4.3)
     base64 (0.2.0)
     benchmark (0.4.0)
     bigdecimal (3.1.9)
@@ -82,7 +82,7 @@ GEM
       rubocop-ast (>= 1.38.0, < 2.0)
       ruby-progressbar (~> 1.7)
       unicode-display_width (>= 2.4.0, < 4.0)
-    rubocop-ast (1.39.0)
+    rubocop-ast (1.40.0)
       parser (>= 3.3.1.0)
     rubocop-rails (2.30.3)
       activesupport (>= 4.2.0)

data/archival_record.gemspec

@@ -22,9 +22,7 @@ Gem::Specification.new do |gem|
                   "Sergey Gnuskov",
                   "Elijah Miller"]
   gem.email    = ["joel.meador+archival_record@gmail.com"]
-  gem.homepage = "https://codeberg.org/joelmeador/archival_record/"
   gem.licenses = ["MIT"]
-
   gem.files = `git ls-files`.split("\n")
   gem.require_paths = ["lib"]
   gem.required_ruby_version = ">= 3.0"
@@ -54,5 +52,16 @@ Gem::Specification.new do |gem|
 
       Additionally, other plugins generally change how destroy/delete work. ArchivalRecord does not, and thus one can destroy records like normal.
     DESCRIPTION
-  gem.metadata["rubygems_mfa_required"] = "true"
+
+  gem.metadata = {
+    "bug_tracker_uri"       => "https://codeberg.org/joelmeador/archival_record/issues",
+    "changelog_uri"         => "https://codeberg.org/joelmeador/archival_record/src/branch/main/CHANGELOG.md",
+    "homepage_uri"          => "https://codeberg.org/joelmeador/archival_record/",
+    "rubygems_mfa_required" => "true",
+    "source_code_uri"       => "https://codeberg.org/joelmeador/archival_record/",
+    # "documentation_uri"     => "https://www.example.info/gems/bestgemever/0.0.1",
+    # "funding_uri"           => "https://example.com/donate"
+    # "mailing_list_uri"      => "https://groups.example.com/bestgemever",
+    # "wiki_uri"              => "https://example.com/user/bestgemever/wiki",
+  }
 end

data/lib/archival_record/version.rb

@@ -1,5 +1,5 @@
 module ArchivalRecord
 
-  VERSION = "4.0.0".freeze
+  VERSION = "4.0.1".freeze
 
 end

data/lib/archival_record_core/archival_record.rb

@@ -1,4 +1,7 @@
+# Namespace for containing core extensions to active record
 module ArchivalRecordCore
+  # Primary holding module for defining our custom errors and the method installer that
+  # gets added to ApplicationRecord
   module ArchivalRecord
 
     require "digest/md5"
@@ -18,6 +21,8 @@ module ArchivalRecordCore
       base.extend ActMethods
     end
 
+    # this defines the class-level methods used to setup the archival record work on a given
+    # class.
     module ActMethods
 
       def archival_record(options = {})

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: archival_record
 version: !ruby/object:Gem::Version
-  version: 4.0.0
+  version: 4.0.1
 platform: ruby
 authors:
 - Joel Meador
@@ -195,7 +195,6 @@ files:
 - ".envrc"
 - ".gitignore"
 - ".rubocop.yml"
-- ".rubocop_todo.yml"
 - Appraisals
 - CHANGELOG.md
 - Gemfile
@@ -263,11 +262,15 @@ files:
 - test/test_helper.rb
 - test/through_association_test.rb
 - test/transaction_test.rb
-homepage: https://codeberg.org/joelmeador/archival_record/
+homepage:
 licenses:
 - MIT
 metadata:
+  bug_tracker_uri: https://codeberg.org/joelmeador/archival_record/issues
+  changelog_uri: https://codeberg.org/joelmeador/archival_record/src/branch/main/CHANGELOG.md
+  homepage_uri: https://codeberg.org/joelmeador/archival_record/
   rubygems_mfa_required: 'true'
+  source_code_uri: https://codeberg.org/joelmeador/archival_record/
 post_install_message:
 rdoc_options: []
 require_paths:

data/.rubocop_todo.yml

@@ -1,7 +0,0 @@
-# This configuration was generated by
-# `rubocop --auto-gen-config`
-# on 2024-06-11 01:38:42 UTC using RuboCop version 1.64.1.
-# The point is for the user to remove these configuration records
-# one by one as the offenses are removed from the code base.
-# Note that changes in the inspected code, or installation of new
-# versions of RuboCop, may require this file to be generated again.