chore(deps): bump the rubygems group with 2 updates

[dependabot]

Bumps the rubygems group with 2 updates: html2rss and base64.

Updates html2rss from 70540c7 to 6d9dcee

Commits

• 6d9dcee fix: avoid zeitwerk to load circular (#268)
• See full diff in compare view

Updates base64 from 0.2.0 to 0.3.0

Release notes

Sourced from base64's releases.

v0.3.0

What's Changed

• Provide a 'Changelog' link on rubygems.org/gems/base64 by @​mark-young-atg in ruby/base64#18
• Exclude older than 2.6 on macos-14 by @​nobu in ruby/base64#21
• Add RBS signature and testing by @​ksss in ruby/base64#25
• Enabled trusted publisher for rubygems.org by @​hsbt in ruby/base64#29
• [DOC] Tweaks for module Base64 by @​BurdetteLamar in ruby/base64#23

New Contributors

• @​mark-young-atg made their first contribution in ruby/base64#18
• @​nobu made their first contribution in ruby/base64#21
• @​ksss made their first contribution in ruby/base64#25

Full Changelog: ruby/base64@v0.2.0...v0.3.0

Commits

• c5d3c7f v0.3.0
• 5f43831 [DOC] Tweaks for module Base64
• bb66095 Enabled trusted publisher for rubygems.org
• cd65c10 Add RBS signature and testing (#25)
• e30df92 Update file list on gemspec
• 9704a4c Update license files same as ruby/ruby
• 7ec2861 Merge pull request #21 from ruby/old-version-on-macos
• 7ae5efd Exclude older than 2.6 on macos-14
• 9669a7d Merge pull request #18 from mark-young-atg/provide_changelog_link_on_rubygems
• 7cab043 Provide a 'Changelog' link on rubygems.org/gems/base64
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ❌ docker-test

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[gildesmarais]

@dependabot recreate

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ❌ docker-test

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ❌ docker-test

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.