Cimas sync 2026-06-29: pubid Ruby 3.3 bump + template refresh

[opoudjis]

Refs metanorma/ci#274

Part of the cimas-sync 2026-06-29 wave bringing the pubid-* family into Ruby-3.3 template-current state.

What this PR carries

• <gem>.gemspec: bumps required_ruby_version to >= 3.3.0. Driven by the centralised patches: ruby_version block in metanorma/ci:cimas-config/cimas.yml.
• .github/workflows/rake.yml: adds workflow-level permissions: contents: write (template-forward, also closes the metanorma/ci#272/#276 Consequence-1 cap-failure mode if anything ever lowered it to read).
• .rubocop.yml: bumps TargetRubyVersion from 2.5 to 3.4 (consistent with the gemspec floor) and updates the riboseinc/oss-guides URL from the master branch to main.
• pubid-nist only: also .github/workflows/release.yml carries a doc-string update for the next_version input (pure documentation, zero behaviour change).

Why bundled

The non-gemspec changes are not unrelated drift — they form a coherent network supporting the Ruby-3.3 ecosystem bump. Linting against Ruby 2.5 idioms while declaring >= 3.3.0 would be incoherent, and the permissions: contents: write is required for the tests-passed cross-workflow dispatch under the post-#315/#316 chain.

Verification

The rake matrix against [3.3, 3.4, 4.0-experimental] (per ruby-matrix.json) should pass green. PR is one of 11 sibling PRs across pubid-bsi, pubid-ccsds, pubid-cen, pubid-core, pubid-iec, pubid-ieee, pubid-iso, pubid-itu, pubid-jis, pubid-nist, pubid-plateau.

🤖

[opoudjis]

Apologies for the spam-PR — closing this and the 10 sibling PRs as superseded by repository deprecation, not because the change is wrong.

What happened

Tonight's cimas-sync wave for metanorma/ci#274 (Ruby 3.3 minimum) targeted the pubid group as named in cimas-config/cimas.yml. After the 11 PRs opened, CI surfaced failing dependent-gems-test runs, and triage revealed that the 11 standalone metanorma/pubid-* repos have been superseded by the metanorma/pubid monorepo.

Evidence:

• metanorma/pubid monorepo contains all relevant gems under gems/pubid-{bsi,ccsds,cen,core,etsi,iec,ieee,iho,iso,itu,jis,nist,plateau}/ plus the umbrella gems/pubid/.
• Monorepo is actively maintained — latest commit 2026-06-26, latest merged PR is metanorma/pubid#80 on 2026-06-26.
• The gem currently on rubygems is pubid-iso 1.15.20 (published 2026-06-26), released from the monorepo.
• This standalone repo's last release tag is v0.7.7 from 2024-08-14 — over 22 months ago.
• This standalone repo's last merged PR (#278) is from 2025-04-22 — over 14 months ago.
• The dependent-gems-test workflow on this repo's main has been failing since at least 2026-06-16 because consumers like relaton-iso look for the live pubid-iso 1.15.x and can't find a compatible version under this repo's 0.7.x lineage.

So the Ruby 3.3 floor bump should go to the monorepo, not here. Action being taken alongside this close:

1. The 11 standalone pubid-* entries are being removed from metanorma/ci:cimas-config/cimas.yml so future cimas-sync waves don't keep targeting deprecated repos. Tracked at metanorma/ci#300 (Gap 3 — cimas-side opt-out detection).
2. The umbrella metanorma/pubid is also being removed from cimas-config until #300 Gap 2 (monorepo sub-template family) lands — the master template's uses: metanorma/ci/.github/workflows/generic-rake.yml@main doesn't fit the monorepo's monorepo: true, gem_directory: gems shape.

The Ruby 3.3 floor for the live pubid-* gems will be picked up by the monorepo's own release cadence, which is on Ruby 3.3+ already.

🤖