cimas sync 2026-07-08: rubocop todo inherit fix + release.yml bundle install - #536
Merged
Conversation
…release_command bundle install) request-checks: true
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Supersedes #535 from prior cimas-sync waves.
Summary
Cimas sync 2026-07-08 — master template corrections for two release-adjacent gaps:
.rubocop.yml— appended.rubocop_todo.ymlas the lastinherit_fromentry so per-gem todos take effect against the shared oss-guides config.inherit_fromis last-wins; the previous ordering left the shared config's stricterMetrics/*rules overriding per-gem grandfathering, and the todo became inert. Empirically verified on suma 2026-07-06: with the todo listed first, 34Metrics/*offenses remained; moved last, cleared. Audit confirmed all 54 gems mapping this template already carry a live.rubocop_todo.yml, so this reference is safe to emit unconditionally. Seemetanorma/ci:a864ed9..github/workflows/release.yml— added explicitrelease_command: | bundle install\n bundle exec rake release, compensating formetanorma/ci#314'sbundler_cachedeprecation (hardcoded tofalsein the release job after the metanorma-cli v1.16.6Bundler::GemNotFound: metanorma-nistincident). Without this override, the reusable's defaultrelease_command: bundle exec rake releasefires against uninstalled gems and fails. Surfaced by @kwkwan on metanorma-plugin-lutaml#285; deeper fix (bundle installinsiderubygems-release.yml's release job itself) tracked atmetanorma/ci#349. Seemetanorma/ci:f994f4c.What to expect on your gem
.rubocop_todo.ymlcovers current offenses: CI stays green..rubocop_todo.ymlhas plugin-drift (missed cops from ci#334'srubocop-rspec/rubocop-performance/rubocop-rakeaddition, or subsequent minor releases of those plugins): CI will red on rubocop-style failures. Fix per-gem:bundle exec rubocop --regenerate-todo— same recipe as sts-ruby / suma on 2026-07-05.release.ymlis template-only: no runtime effect until the gem's next release, at which point the two-linerelease_commandkicks in and fixes the missing-bundle-install failure that was silent-broken before.Wave discipline
--flatten-stalefull auto-close of prior stalecimas-sync-*wave branches on this repo.🤖