custodian-core 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f7964e4623e30dd16ef4b7c9dd708f49d143ecfd98146470b7a78eb582dcebea
-  data.tar.gz: e068635b45a959416e80289cc36bb6fe2e3cb3a93fa89b81ce48a81c63c38b7a
+  metadata.gz: 71316efbb9b0ae0177deed2ebef9e748f2b3a60b9d0094fe4ecd3014b0613b3e
+  data.tar.gz: f9b4561451dee601718a5c4a630769833184385b6d938c700813b2e44aadb953
 SHA512:
-  metadata.gz: a49ad921937a9c02817bea8da23c8761daa3c3a5af18dddb017d8853cf7fe01b7bf03b6a469e6a1c263f73043fd47af55dcda1dd509776f6a8d464bb460e4179
-  data.tar.gz: 96b332f0053a92e41c503ef9e2417228ead9dd52aeb8f1521a51c8e4c7c5c0c69b239b9eccd7002d154cf671807b14f3d53c5140778cde9e7902ce302bbad8bc
+  metadata.gz: 2584e0341431d11a50a9b8d0b60a318ece85e5ea18bcbf52adf0394a4cb4cc7b01ad84e516ae16bfa8de39ae5711ad36897b5a4f21f0e29a9b931f9f2d2c4515
+  data.tar.gz: 8192415af6f9bd5ccbe607e748fa26f624eceb3bea99c8c872b1a145ab8221704e90a758becae6f433e9675218df01eedc0c12ef0126f9840122c9ca2ae2bcf7

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 ## [Unreleased]
 
+## [0.1.1] - 2026-08-19
+
+### Security and release hardening
+
 - Require Ruby 3.2+, support Rails 7.x/8.x and ancestry 4.x/5.x explicitly.
 - Reject negative demands and non-finite, negative, or over-remaining numeric
   action outcomes.
@@ -7,6 +11,20 @@
   traverse deep trees iteratively.
 - Limit the built gem to consumer-facing code, migrations, signatures, and
   top-level release documentation.
+- Add repository-wide CODEOWNERS coverage.
+- Default GitHub Actions permissions to read-only and restrict `id-token: write`
+  to the publication job.
+- Pin GitHub Actions to full commit SHAs and configure Dependabot updates for
+  GitHub Actions.
+- Strengthen protection of the `main` and `dev` branches.
+- Publish through GitHub Actions Trusted Publishing and RubyGems OIDC.
+
+### Release pipeline fixes
+
+- Correct release-tag ancestry validation by fetching the complete history and
+  checking that the tagged commit belongs to `main`.
+- Use Ruby 3.4 for releases to avoid the publication conflict observed with
+  Ruby 3.2.
 
 ## [0.1.0] - 2026-07-07
 

data/README.md

@@ -165,17 +165,16 @@ Planned extensions that do not exist in this gem yet:
 `ancestry` 4.x and 5.x. The lower Ruby bound keeps the supported runtime
 aligned with the CI matrix and with the currently supported Rails majors.
 
-This gem is not published to RubyGems yet. While it lives on GitHub only,
-add it to your host Rails application's Gemfile via git:
+Add the gem to your host Rails application's Gemfile:
 
 ```ruby
-gem "custodian-core", git: "https://github.com/lucasnssoftwareengineer-alt/custodian-core"
+gem "custodian-core", "~> 0.1.1"
 ```
 
-Once it is published to RubyGems, this becomes simply:
+Then install it:
 
-```ruby
-gem "custodian-core"
+```sh
+bundle install
 ```
 
 Then install the engine's migrations:

data/custodian-core.gemspec

@@ -5,7 +5,7 @@ require_relative "lib/custodian/core/version"
 Gem::Specification.new do |spec|
   spec.name = "custodian-core"
   spec.version = Custodian::Core::VERSION
-  spec.authors = ["Lucas nunes de sousa"]
+  spec.authors = ["Lucas Nunes de Sousa"]
   spec.email = ["lucas.ns.software.engineer@gmail.com"]
   spec.homepage = "https://github.com/lucasnssoftwareengineer-alt/custodian-core"
   spec.metadata["source_code_uri"] = "https://github.com/lucasnssoftwareengineer-alt/custodian-core"

data/lib/custodian/core/version.rb

@@ -2,6 +2,6 @@
 
 module Custodian
   module Core
-    VERSION = "0.1.0"
+    VERSION = "0.1.1"
   end
 end

metadata

@@ -1,10 +1,10 @@
 --- !ruby/object:Gem::Specification
 name: custodian-core
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
-- Lucas nunes de sousa
+- Lucas Nunes de Sousa
 bindir: exe
 cert_chain: []
 date: 1980-01-02 00:00:00.000000000 Z