Skip to content

Add MiniMax + harness announcements and a scheduled Discord auto-poster#2

Merged
Rod-Christensen merged 7 commits into
rocketride-org:mainfrom
mithileshgau:add-minimax-cloud-launch-announcements
Jun 9, 2026
Merged

Add MiniMax + harness announcements and a scheduled Discord auto-poster#2
Rod-Christensen merged 7 commits into
rocketride-org:mainfrom
mithileshgau:add-minimax-cloud-launch-announcements

Conversation

@mithileshgau

@mithileshgau mithileshgau commented Jun 5, 2026

Copy link
Copy Markdown
Collaborator

Announcements-feed update, in three parts:

1. New announcements (announcements.json)

rocketride-minimax-m3-2026 — RocketRide × MiniMax partnership; M3 open-weights model live as an open-source pipeline node.
rocketride-harness-engineering-demo-2026 — SCALE Demo Day demo (sub-30s offline pipeline, 64-thread C++ runtime).
Both bodies are kept to ≤2 sentences with no emoji, and both use the RocketRide logo from assets/.

2. CI fix (validate.yml)

Fixed the unique-id check, which errored on every run since the scaffold

3. Docs (README.md)

Documented the title/body authoring conventions: bodies ≤2 sentences, no emoji, and visuals committed to assets/ and referenced via Markdown image syntax rather than inline emoji.

Notes

No schema changes — the field set is unchanged.
Discord auto-poster removed for now. It needs more brainstorming, so it'll come back as its own focused PR rather than riding along here.

…ncements

Adds three info announcements (valid 2026-06-04 → 2026-06-11):
- rocketride-minimax-m3-2026: RocketRide × MiniMax partnership; M3
  open-weights model live as an open-source pipeline node
- rocketride-cloud-launch-rho-2026: RocketRide Cloud launch June 18 at
  SHACK15 with Rho as official Launch Night partner
- rocketride-harness-engineering-demo-2026: Joe Maionchi's SCALE Demo
  Day live demo — sub-30s offline pipeline, C++ runtime, 64 threads

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Drop rocketride-cloud-launch-rho-2026 entry
- Add discord_post_at to the remaining four (MiniMax posts tomorrow
  9am PT, the rest backdated to 2026-06-03 9am PT)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mithileshgau mithileshgau deleted the add-minimax-cloud-launch-announcements branch June 5, 2026 06:59
@mithileshgau mithileshgau restored the add-minimax-cloud-launch-announcements branch June 5, 2026 07:01
@mithileshgau mithileshgau reopened this Jun 5, 2026
@mithileshgau mithileshgau changed the title add: MiniMax M3 partnership, Cloud launch, and harness demo(SCALE) announcement Add MiniMax + harness announcements and a scheduled Discord auto-poster Jun 5, 2026
Mithilesh Gaurihar and others added 3 commits June 5, 2026 00:07
GitHub Action that posts announcements.json entries to a Discord channel
on an hourly schedule, gated by discord_post_at / valid_from / valid_until
and deduped via a committed-back ledger (.discord/posted.json).

- discord-post.yml: hourly cron + manual workflow_dispatch
- post-to-discord.sh: rich-embed default, or verbatim plain message via
  optional discord_content (@everyone, custom emoji, raw URLs)
- DISCORD_SETUP.md: setup + scheduling/formatting docs
- requires repo secret DISCORD_ANNOUNCEMENT_WEBHOOK_URL

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Removes the MiniMax id from the posted ledger so the hourly poster sends it
at its discord_post_at (2026-06-05T16:00:00Z / 9am PT). The other three stay
seeded so enabling the workflow won't re-post them.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Switches the MiniMax Discord post from the default embed to a plain
@everyone message with the RocketRideiconWhite custom emoji and bullet
highlights. Extension copy (title/body) is unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

@Rod-Christensen Rod-Christensen left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please combine update this PR with the fix you included in the next PR so they are one unit of work. Also, if you are going to add fields to the schema, update README.md documenting the fields added or changed.

Try to limit the body text to 2 sentences and don't use emojis -- that really cheapens the product. If you want a graphic, but it in assets and reference it in the markdown code.

Mithilesh Gaurihar and others added 2 commits June 8, 2026 00:00
The check piped .announcements[].id into a comparison, then referenced
.announcements again on the right of the pipe — but after the pipe jq has
rebound . to the id array, so the second .announcements indexed an array
with a string and aborted:

  jq: error: Cannot index array with string "announcements"

It failed for every valid announcements.json since the scaffold, so id
uniqueness was never actually enforced. Bind the id list once with
`as $ids` and compare its length to its deduped length so the filter
parses and the check works.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Drop the Discord auto-poster entirely: discord-post.yml, the poster
  script, the ledger, DISCORD_SETUP.md, and the discord_post_at /
  discord_content fields on announcements
- Rewrite MiniMax and harness bodies to <=2 sentences with no emoji;
  give the harness entry the RocketRide logo
- Document body/title conventions (<=2 sentences, no emoji, graphics via
  assets referenced in Markdown) in README

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mithileshgau

Copy link
Copy Markdown
Collaborator Author

@Rod-Christensen, Thanks for the review! Made the changes:

  • Pulled the CI fix into this PR so it's all one unit of work.
  • Trimmed the announcement bodies to 2 sentences and removed the emojis. Also noted in the README that graphics should go in assets/ and be referenced in Markdown.
  • Removed the Discord automation for now, it needs more thought, so I'll do it as its own PR. No new schema fields as a result.

@Rod-Christensen Rod-Christensen merged commit 9bc1e6d into rocketride-org:main Jun 9, 2026
1 check passed
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.

2 participants