Why Contribute Upstream
Every GlacierPhonk bot runs on grammY. The framework handles update routing, middleware, sessions, conversations, and the entire Telegram Bot API surface. When you depend on something this deeply, contributing back is not charity — it is maintenance. Bugs you fix upstream are bugs that never hit your production bots. CI you improve upstream means faster releases that you depend on.
We had been reading the grammY source for months while building bots. Familiarity with the internals made it natural to spot things that could be improved.
PR #881 — Fixing a Filter Bug
The first contribution was a real bug. In src/filter.ts, the MESSAGE_KEYS registry contained a typo introduced in commit 387bf9a when Bot API 9.4 support was added. One missing letter:
// Before (broken)
"chat_owner_changd"
// After (fixed)
"chat_owner_changed"
The typo meant that bot.on("message:chat_owner_changed", ...) would silently fail filter validation. The handler would register but never fire, because the filter key in the registry did not match the correct Telegram Bot API field name. Types would compile. Events would pass through unmatched. No error, no warning.
A single-character fix. The kind of bug that is trivial to patch but non-obvious to diagnose. Reviewed and merged the same day.
PR #883 — CI Modernization
The second contribution targeted the CI pipeline. Two GitHub Actions in the grammY workflow were running outdated major versions:
codecov/codecov-actionwas on v1.0.10 — upgraded to v5, with thefileparameter renamed tofilesto match the v5 APIsoftprops/action-gh-releasewas on v1 — upgraded to v2
Both v1 versions were several years behind, missing security patches and compatibility updates. The upgrades were backward compatible — verified against the current workflow configuration before submitting. Also merged the same day.
Contributor Status
With both PRs merged, GlacierPhonk is now listed as an official contributor to grammY on GitHub. A small milestone, but a real one. It means the studio is not just consuming open source — it is contributing to the infrastructure it depends on.
This is how you build credibility in a technical community. Not by announcing yourself, but by showing up in the commit log.
2 PRs merged. 1 contributor badge.