Skip to content

Regenerate gemspec (ensuring parslet range is up-to-date) - #57

Open
maxfierke wants to merge 1 commit into
SmartBear:masterfrom
maxfierke:mf-update_parslet_dep
Open

Regenerate gemspec (ensuring parslet range is up-to-date)#57
maxfierke wants to merge 1 commit into
SmartBear:masterfrom
maxfierke:mf-update_parslet_dep

Conversation

@maxfierke

Copy link
Copy Markdown

Resolves #55. It appears that rake gemspec needed to be re-run after 2bc026c037566040e93c51d9715008a8e2ab83ec was merged

yildizsc added a commit to socio-labs/ruby-handlebars that referenced this pull request Sep 1, 2026
Ruby 4.0 reduced core cgi to a shim around cgi/escape that warns under
$VERBOSE. The HTML escaper now requires cgi/escape directly - warning-free,
and no external cgi gem needed. A guarded fallback keeps JRuby working, where
cgi/escape does not define CGI.escapeHTML on its own.

The bigger fix: the gemspec declared parslet "~> 1.6" while the Gemfile,
lockfile and CI had all used parslet 2.0 since 2022. That generator drift
pinned every consumer to parslet 1.8.2, unmaintained since 2020. Upstream
issue SmartBear#55, submitted twice as PRs SmartBear#57 and SmartBear#65, never merged. Now "~> 2.0".

Drops juwelier for a hand-maintained gemspec - it caused that drift and cannot
run on Ruby 3.2+. required_ruby_version stays ">= 2.7" so no existing consumer
is dropped; CI covers 2.7 through 4.0 plus JRuby, pinned to ubuntu-24.04
because no ubuntu-26.04 builds exist below Ruby 3.3.

Not published to RubyGems - that name is upstream's. Consumers pin a tag:

    gem 'ruby-handlebars', github: 'socio-labs/ruby-handlebars', tag: '0.5.0'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update ruby-handlebars gemspec to use parslet 2

1 participant