github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-07-16 14:42:29 -05:00
Code Issues 276 Packages Projects Releases 26 Wiki Activity

[PR #1832] [MERGED] feat(captions): upgrade MiniMax example to M3 default #27302

New Issue
Closed
opened 2026-06-18 16:53:31 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-06-18 16:53:31 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/harvard-edge/cs249r_book/pull/1832
Author: @octo-patch
Created: 6/3/2026
Status: ✅ Merged
Merged: 6/10/2026
Merged by: @profvjreddi

Base: dev ← Head: feature/upgrade-minimax-m3

📝 Commits (1)

  • 4a8c4b9 feat: upgrade MiniMax default model example to M3

📊 Changes

1 file changed (+2 additions, -2 deletions)

View changed files

📝 book/tools/scripts/content/manage_captions.py (+2 -2)

📄 Description

Summary

Upgrade the manage_captions.py docstring example to reference the latest MiniMax model (MiniMax-M3) instead of MiniMax-M2.7, so first-time users land on the current flagship model.

Changes

  • Update the --provider minimax usage example in the script's epilog to use MiniMax-M3 (was MiniMax-M2.7)
  • No code logic changes; the model name is user-supplied via --model and the example was the only place the model ID was pinned

Why

MiniMax released M3, the new default flagship: 512K context window, up to 128K output tokens, and image input support on the OpenAI-compatible endpoint. The previous example pinned M2.7 (added in #1239), which is still available but is no longer the recommended starting point. M2.7 / M2.7-highspeed remain valid --model values for anyone who prefers them.

Testing

  • Verified the docstring example renders correctly (python book/tools/scripts/content/manage_captions.py --help)
  • No other MiniMax / minimax provider references in the file were affected

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/harvard-edge/cs249r_book/pull/1832 **Author:** [@octo-patch](https://github.com/octo-patch) **Created:** 6/3/2026 **Status:** ✅ Merged **Merged:** 6/10/2026 **Merged by:** [@profvjreddi](https://github.com/profvjreddi) **Base:** `dev` ← **Head:** `feature/upgrade-minimax-m3` --- ### 📝 Commits (1) - [`4a8c4b9`](https://github.com/harvard-edge/cs249r_book/commit/4a8c4b9ffdd506cc4212c38ca05a3f9dd797abff) feat: upgrade MiniMax default model example to M3 ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `book/tools/scripts/content/manage_captions.py` (+2 -2) </details> ### 📄 Description ## Summary Upgrade the `manage_captions.py` docstring example to reference the latest MiniMax model (`MiniMax-M3`) instead of `MiniMax-M2.7`, so first-time users land on the current flagship model. ## Changes - Update the `--provider minimax` usage example in the script's epilog to use `MiniMax-M3` (was `MiniMax-M2.7`) - No code logic changes; the model name is user-supplied via `--model` and the example was the only place the model ID was pinned ## Why MiniMax released M3, the new default flagship: 512K context window, up to 128K output tokens, and image input support on the OpenAI-compatible endpoint. The previous example pinned M2.7 (added in #1239), which is still available but is no longer the recommended starting point. M2.7 / M2.7-highspeed remain valid `--model` values for anyone who prefers them. ## Testing - Verified the docstring example renders correctly (`python book/tools/scripts/content/manage_captions.py --help`) - No other MiniMax / minimax provider references in the file were affected --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-06-18 16:53:31 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: book
area: collabs
area: kits
area: labs
area: socratiq
area: staffml
area: tinytorch
area: tools
area: website
bug
dependencies
format: epub
format: pdf
javascript
link-health
link-rot
priority-high
pull-request
Mirrored from GitHub Pull Request
 staffml
type: bug
type: citation
type: code
type: errata
type: improvement
type: new
type: question
vault-sli
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#27302
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?