chore(deps): admit rouge 5 + refresh the dogfood site's dependencies - #54
Merged
Conversation
… packages The gemspec's rouge `< 5` cap silently DOWNGRADED consuming sites already on rouge 5.x (daisyui's docs app went 5.0.0 -> 4.7.0 during the 1.0.3 rollout). Widen to `< 6` — the full component suite (736 examples, incl. the ~12-lexer Code specs + inline theme CSS) passes against rouge 5.0.0. Dogfood site refreshed to prove the pairing end-to-end: - gems: rouge 5.0.0, daisyui 1.2.1, playwright-ruby-client 1.61.0 (+ strscan, rouge 5's dep) - node: tailwindcss/@tailwindcss/cli 4.3.2, daisyui 5.6.13, playwright 1.61.1 - CSS rebuilt (daisyUI 5.6.13); docs suite 15/15 incl. Playwright system specs All other gemspec runtime constraints already admit their latest (phlex-rails 2.4, rails_icons 1.9, commonmarker 2.8, nokogiri 1.19, zeitwerk 2.8) — no widening needed. Claude-Session: https://claude.ai/code/session_01FPQb6z3YwcKRMbvoJhdxnX
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.
Summary
Follow-up from the 1.0.3 dogfood rollout: docs-kit's rouge
>= 4.0, < 5cap was silently downgrading consuming sites already on rouge 5.x (daisyui's docs app went 5.0.0 → 4.7.0 when it adopted the released gem).>= 4.0, < 5→>= 4.0, < 6— verified against the full component suite (736 examples, including the multi-lexerDocsUI::Codespecs and the inline theme CSS) running rouge 5.0.0bundle update: rouge 5.0.0, daisyui 1.2.1, playwright-ruby-client 1.61.0 (+strscan, rouge 5's new dep)bun update --latest: tailwindcss + @tailwindcss/cli 4.1.18 → 4.3.2, daisyui 5.6.0 → 5.6.13, playwright 1.50 → 1.61.1All other gemspec runtime constraints already admit their latest versions (phlex-rails 2.4, rails_icons 1.9, commonmarker 2.8, nokogiri 1.19, zeitwerk 2.8) — no other widening needed.
Verification
bundle exec rubocop— no offensesAfter merging
Release (e.g.
rake release[1.0.4]) so consuming sites canbundle update docs-kit rougeand get rouge 5 back — daisyui is the one currently pinned down to 4.7.0 by this constraint.https://claude.ai/code/session_01FPQb6z3YwcKRMbvoJhdxnX