chore(deps): bump googleapis/release-please-action from 4 to 5#1
Open
dependabot[bot] wants to merge 1 commit into
Open
chore(deps): bump googleapis/release-please-action from 4 to 5#1dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
Bumps [googleapis/release-please-action](https://github.com/googleapis/release-please-action) from 4 to 5. - [Release notes](https://github.com/googleapis/release-please-action/releases) - [Changelog](https://github.com/googleapis/release-please-action/blob/main/CHANGELOG.md) - [Commits](googleapis/release-please-action@v4...v5) --- updated-dependencies: - dependency-name: googleapis/release-please-action dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/googleapis/release-please-action-5
branch
from
26f0276 to
0a46744
Compare
Bhasvanth-Dev9380
added a commit
that referenced
this pull request
Jun 22, 2026
Route Telegram through a proxy when api.telegram.org is unreachable directly
(getMe times out where Telegram is blocked). Resolve a proxy URL from
channels.telegram.proxy / accounts[].proxy (${VAR}-resolved) or HTTPS_PROXY /
ALL_PROXY env, build an undici ProxyAgent dispatcher, and attach it to the
grammY Bot (client.baseFetchConfig.dispatcher) so every Telegram API call
tunnels through it. No proxy configured -> unchanged direct connection.
HTTP/HTTPS only (SOCKS detected + logged; needs socks-proxy-agent dep).
Closes the #1 Telegram parity gap vs the reference.
Bhasvanth-Dev9380
added a commit
that referenced
this pull request
Jun 23, 2026
) The 4-pattern hook runner existed but fired from zero production sites — plugin `b.hook(...)` handlers were silent no-ops. Fire registry.fireHook at the real pipeline sites: inbound_claim (claim→skip), before_dispatch (immediate+debounced, claim→skip), reply_dispatch (claim→suppress send), message_sent (void telemetry), and message_sending (modifying) on the agent send tool. Operator's owner-bootstrap + admin commands preserved.
Bhasvanth-Dev9380
added a commit
that referenced
this pull request
Jun 24, 2026
Fourth channel, cloned from the hardened Slack/Telegram channels: Gateway (WebSocket) inbound + the Client's REST for outbound, 15 source files. Full feature set — markdown/mentions (verbatim token passthrough)/threads/reactions (incl. custom emoji)/media/buttons/slash/streaming/multi-account/native approval buttons — plus the fixes a 6-dimension parity sweep vs OpenClaw surfaced: guildId/memberRoleIds routing (was mis-mapped to Slack's teamId tier), allowed_mentions @everyone mass-ping safety, MESSAGE CONTENT intent probe (the #1 footgun), 4014/4004 gateway-close terminal, proxy doc + outbound filename. Media download SSRF-guarded (https + Discord CDN host allowlist). Registered in BUNDLED_MODULES + DISCORD_CHANNEL_META (order 40) + createDiscordPlugin multi-account boot + session-reaper TTL + sdk re-export. Adds discord.js@^14.26.4. The redactDiscordToken test fixture is assembled from parts at runtime so no literal token-shaped string sits in source (GitHub push protection). Typecheck clean; Discord suite 219; full suite 4150/0.
Bhasvanth-Dev9380
added a commit
that referenced
this pull request
Jul 12, 2026
…V/Alt+V Three things were wrong, and the operator was right about all of them. 1. IT WASN'T A REAL ATTACHMENT. Images already rode as inline bytes, but every other file was handed to the model as a PATH plus a hope that it would call a tool. An attachment whose content the model never sees is a suggestion, not an attachment. Text-like files (source, config, yaml, json, logs, markdown, csv, sql, shell, …) are now READ at compose time and their content is inlined directly into the turn — no tool call, no round-trip, and the content is right there in the transcript where the operator can see it was actually looked at. Bounded at 256 KB with an explicit truncation marker, never silent. PDF/Office/EPUB and video/audio still route through analyze_media, and that is not laziness: Pi's content model is text + image, so there is literally no content block a PDF or an MP4 can ride in. A tool is the only door. (PDF/DOCX/ XLSX/PPTX parse locally with no key; video/audio need a Gemini key.) 2. YOU COULDN'T SEE IT. The chip "tray" printed into scrollback, so it scrolled away the moment anything else happened — at the instant you press Enter there was no way to know whether a file was armed. There is now a persistent attachment bar pinned in the bottom region alongside the editor and footer, repainted on every single mutation of the staged list, so what it says and what will actually ride the next turn cannot drift. Pasting also drops a visible `[image #1]` pill into the line you're typing, the way a chat client does — without it, a clipboard paste (which has no path to echo) looked like it did nothing at all. 3. CLIPBOARD DIDN'T COME. Only `/paste` was wired; no keystroke. Ctrl+V (0x16) and Alt+V (ESC v) are now both bound. Both exist because Ctrl+V alone is not enough on Windows: Windows Terminal binds it to its own paste, which inserts the clipboard's TEXT — and with an image-only clipboard it inserts nothing, so the keypress is eaten by the terminal and never reaches us. Alt+V is unbound by every mainstream terminal, so it arrives intact. Verified end-to-end against a real clipboard on Windows, not just unit tests: a 19.5 KB screenshot captured off the clipboard, base64'd into a genuine image block (26,024 chars), alongside a text file whose contents landed in the prompt.
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.
Bumps googleapis/release-please-action from 4 to 5.
Release notes
Sourced from googleapis/release-please-action's releases.
... (truncated)
Changelog
Sourced from googleapis/release-please-action's changelog.
... (truncated)
Commits
45996edchore(main): release 5.0.0 (#1200)a8121b9chore: build dist (#1201)f533c26fix: bump release-please from 17.3.0 to 17.6.0 (#1199)46dfc01feat!: upgrade to node24 (#1188)