Code changes, week of 2026-10-12 – 2026-10-18 · 28 commits

What it is: Code activity
Where HEY read it: GitHub · Commits that week ↗ · Repository ↗
When it happened: In the week of Mon 2026-10-12 – Sun 2026-10-18 (UTC), dated by the source to the week
HEY first saw it: 2026-10-12 (33d ago)These are two different clocks: when the work happened, as the source dates it, and when HEY first read it. A week of code activity is one record, which HEY writes when it first sees the week and keeps up to date while the week runs, so HEY can first see it before the week ends.
What changed that week: 28 commits that week, not counting automation or merges.
update placeholder card for rewards page 2026-10-15
rub-3252, remove hadrcoded link value 2026-10-15
update eligibility request params 2026-10-13
How it is backed: Source-backed
Counts toward building: Yes. It is one of the records HEY’s activity status is built from.
Records behind it: Github repo, read 2026-10-12 ↗
What it does not say: A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

Follow Rubic App to see the next change HEY records, with its evidence.

Cite this

Absolute dates in UTC and a link that does not move.

Rubic App: Code changes, week of 2026-10-12 – 2026-10-18 · 28 commits
Happened: in the week 2026-10-12 to 2026-10-18 (UTC)
Source: GitHub, https://github.com/cryptorubic/rubic-app/commits?since=2026-10-12T00%3A00%3A00.000Z&until=2026-10-19T00%3A00%3A00.000Z
Recorded by HEY Research Lab: 2026-10-12 (UTC); accessed 2026-11-14 (UTC)
Evidence ship:f7e9b83c-c1b9-4972-8a43-b79655e44056: https://heyresearch.xyz/evidence/ship:f7e9b83c-c1b9-4972-8a43-b79655e44056
  Receipt: https://heyresearch.xyz/api/evidence/ship%3Af7e9b83c-c1b9-4972-8a43-b79655e44056

Evidence id ship:f7e9b83c-c1b9-4972-8a43-b79655e44056As data How HEY works