Skip to content

feat: distribute managed Hermes patches - #3

Closed
gnezim wants to merge 2 commits into
mainfrom
feat/bundled-telegram-patches
Closed

gnezim wants to merge 2 commits into
mainfrom
feat/bundled-telegram-patches

Conversation

@gnezim

@gnezim gnezim commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add a bundled managed-patch registry alongside the existing local registry
  • ship the Telegram hidden-link patch tied to its upstream PR lifecycle
  • let same-named local patch pairs override bundled assets
  • keep bundled patches immutable during 3-way application
  • include bundled assets in workflow freshness checks and documentation
  • drop the unrelated custom Telegram Bot API NO_PROXY patch; Thunder Forge bypass is configured in the local Hermes .env instead

Validation

  • bash syntax checks pass for all workflow scripts
  • the hidden-link patch remains applied in the live Hermes checkout
  • its focused regression test passes
  • Thunder Forge proxy resolution returns direct after loading the local Hermes .env
  • git diff --check passes

Upstream tracking

@coderabbitai

coderabbitai Bot commented Aug 27, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 99f5e36f-fb1e-4fa1-8a62-e9446476b530


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gnezim gnezim closed this Aug 27, 2026
@gnezim gnezim reopened this Aug 27, 2026
@gnezim gnezim closed this Aug 27, 2026
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.

1 participant