feat: granite4.1 by avinash2692 · Pull Request #964 · generative-computing/mellea

avinash2692 · 2026-04-29T18:55:21Z

Misc PR

Type of PR

Bug Fix
New Feature
Documentation
Other

Description

Summary

Add IBM_GRANITE_4_1_3B, IBM_GRANITE_4_1_8B, IBM_GRANITE_4_1_30B, and IBM_GRANITE_GUARDIAN_4_1_8B model identifiers to the registry
Switch the default model across the framework from granite-4.0-micro (3B) to granite-4.1-3b
Update all Ollama tags from granite4:micro / granite4:micro-h to granite4.1:3b
Update documentation, examples, CI workflows, and test fixtures to reference the new model

What changed

Area	Change
`mellea/backends/model_ids.py`	Added 4 new `ModelIdentifier` constants for 4.1
`mellea/stdlib/session.py`	Default model → `IBM_GRANITE_4_1_3B`
`mellea/backends/ollama.py`	Default model → `IBM_GRANITE_4_1_3B`
`mellea/backends/litellm.py`	Default model string → `IBM_GRANITE_4_1_3B`
`cli/eval/runner.py`	Fallback model → `IBM_GRANITE_4_1_3B`
`.github/workflows/quality.yml`	`ollama pull granite4.1:3b`
`test/conftest.py`	Deduplicated model lists, updated to `granite4.1:3b`
`test/scripts/`	Updated OLLAMA_MODEL_LIST + VLLM_MODEL
25+ docs pages	`granite4:micro(-h)` → `granite4.1:3b`
Examples & notebooks	Updated model references

What was NOT changed (intentional)

Intrinsics code — no 4.1 LoRA adapters exist yet; intrinsics examples/tests/constants remain on granite-4.0-micro
IBM_GRANITE_4_MICRO_3B constant — kept for backward compatibility
IBM_GRANITE_4_HYBRID_MICRO — hybrid model unaffected, Ollama tag unchanged

Testing

Tests added to the respective file if code was changed
New code has 100% coverage if code as added
Ensure existing tests and github automation passes (a maintainer will kick off the github automation when the rest of the PR is populated)

Attribution

AI coding assistants used

github-actions · 2026-04-29T18:55:39Z

The PR description has been updated. Please fill out the template for your PR to be reviewed.

nrfulton

We should probably clean up the docs and code-base if we have specific model ids showing up this often.

nrfulton · 2026-04-29T19:57:17Z

+IBM_GRANITE_4_1_3B = ModelIdentifier(
+    hf_model_name="ibm-granite/granite-4.1-3b",
+    ollama_name="granite4.1:3b",
+    watsonx_name=None,


Remove these Nones.

nrfulton · 2026-04-29T20:01:18Z

+IBM_GRANITE_4_1_3B = ModelIdentifier(
+    hf_model_name="ibm-granite/granite-4.1-3b",
+    ollama_name="granite4.1:3b",
+    watsonx_name=None,


remove these Nones.

avinash2692 · 2026-04-29T20:30:03Z

We should probably clean up the docs and code-base if we have specific model ids showing up this often.

Not sure I quite follow. Are we talking about instances of Granite4.0 in docs?

ajbozarth

A few things to fix before this merges.

Commit hygiene (blocking)
Commits are missing Signed-off-by (git commit -s, AGENTS.md §6) and Assisted-by: Claude Code (AGENTS.md §7). The PR will be squash-merged, so at least one commit needs both trailers before then.

Tests (non-blocking)
No new unit tests for the four new ModelIdentifier constants — checklist box is unchecked.

ajbozarth · 2026-04-29T20:40:01Z

 ## Hello world

 By default, `start_session()` connects to Ollama and uses **IBM Granite 4 Micro**
-(`granite4:micro`). Make sure Ollama is running before you run this:


Branding mismatch. granite4.1:3b is Granite 4.1, not "Granite 4 Micro" — that name belonged to 4.0-micro. This line and line 85 should be updated, e.g. to IBM Granite 4.1 3B.

ajbozarth · 2026-04-29T20:40:01Z


-`start_session()` defaults to **Ollama** with **IBM Granite 4 Micro** (`granite4:micro`).
+`start_session()` defaults to **Ollama** with **IBM Granite 4 Micro** (`granite4.1:3b`).
 No API keys needed — just have Ollama running:


Same branding mismatch: points to granite4.1:3b but still says "IBM Granite 4 Micro".

ajbozarth · 2026-04-29T20:40:01Z

 `start_session()` connects to Ollama on `localhost:11434` and uses
-**IBM Granite 4 Micro** (`granite4:micro`) by default. On first run, Mellea
+**IBM Granite 4 Micro** (`granite4.1:3b`) by default. On first run, Mellea
 automatically pulls the model if it is not already downloaded:


Same branding mismatch.

ajbozarth · 2026-04-29T20:40:01Z


 **Default backend:** `start_session()` with no arguments connects to a local
 [Ollama](https://ollama.ai) instance running **IBM Granite 4 Micro**
-(`granite4:micro`). Make sure Ollama is running before you execute any example.


Same branding mismatch.

ajbozarth · 2026-04-29T20:40:01Z

+
+IBM_GRANITE_GUARDIAN_4_1_8B = ModelIdentifier(
+    hf_model_name="ibm-granite/granite-guardian-4.1-8b"
+)


The "removing Nones" fixup dropped ollama_name=None, # TBD from IBM_GRANITE_GUARDIAN_4_1_8B entirely — there's no longer any indication that Ollama support is pending vs. not applicable. Also, all four new constants now use a compact single-line style inconsistent with every other constant in the file. Suggest reverting to multi-line with ollama_name=None, # not yet available for the guardian.

there's no longer any indication that Ollama support is pending vs. not applicable.

@avinash2692 Granite 4.1 is on ollama: https://ollama.com/library/granite4.1

ajbozarth · 2026-04-29T20:40:01Z

-          ollama pull granite4:micro
-          ollama pull granite4:micro-h
+          ollama pull granite4.1:3b
      - name: Run Tests


granite4:micro-h was dropped from the pull list. Confirm no ollama-marked integration tests still use IBM_GRANITE_4_HYBRID_MICRO, or they'll cold-start/fail in CI.

Yup, I think I confirmed that in a nightly run.

ajbozarth · 2026-04-29T20:40:02Z

            )
-            for model in ["granite4:micro", "granite4:micro-h", "granite3.2-vision"]:
+            for model in ["granite4.1:3b", "granite3.2-vision"]:
                try:


Same concern: granite4:micro-h removed from the warm-up and eviction loops. Please verify no ollama-marked tests depend on the hybrid model being warm.

ajbozarth · 2026-04-29T20:42:22Z

I believe all the items Claude found are either docs that could be handled in a follow up or non-issues, but it's worth double checking

avinash2692 · 2026-04-29T22:36:37Z

waiting on #970 to be resolved.

avinash2692 · 2026-04-29T22:37:39Z

I believe all the items Claude found are either docs that could be handled in a follow up or non-issues, but it's worth double checking

Yea, I think there are some branding/docs issues there. Like @nrfulton mentioned (and if I understood what he said there) I think we might have to clean up model names in docs quite a bit.

* updating core to granite4.1 * updating core to granite4.1 * updating tests to granite4.1 * updating ci to granite4.1 * adding 4.1 to all the docs * missed one * missed some more * removing Nones * adding xfail to a flaky test * setting watsonx name to none to ignore it in tests * temp hack for watsonx backend * adding warning to docstring

avinash2692 added 5 commits April 29, 2026 11:25

updating core to granite4.1

a2aac9d

updating core to granite4.1

f2b5640

updating tests to granite4.1

fcd2459

updating ci to granite4.1

b37f074

adding 4.1 to all the docs

f00bc6f

avinash2692 changed the title ~~Avi/feat/granite4.1~~ feat: granite4.1 Apr 29, 2026

github-actions Bot added the enhancement New feature or request label Apr 29, 2026

avinash2692 marked this pull request as ready for review April 29, 2026 18:57

avinash2692 requested a review from a team as a code owner April 29, 2026 18:57

avinash2692 requested review from ajbozarth and nrfulton April 29, 2026 18:57

avinash2692 added 2 commits April 29, 2026 12:24

missed one

fa95e50

missed some more

f4c89cf

nrfulton approved these changes Apr 29, 2026

View reviewed changes

removing Nones

f81d6c8

avinash2692 requested a review from nrfulton April 29, 2026 20:34

ajbozarth reviewed Apr 29, 2026

View reviewed changes

avinash2692 added 2 commits April 29, 2026 14:04

adding xfail to a flaky test

eeb79cc

setting watsonx name to none to ignore it in tests

f8597fd

avinash2692 added 4 commits April 29, 2026 17:41

temp hack for watsonx backend

642339c

adding warning to docstring

50c4b87

Merge remote-tracking branch 'origin/main' into avi/feat/granite4.1

427ea3c

Merge remote-tracking branch 'origin/main' into avi/feat/granite4.1

a502aea

avinash2692 added this pull request to the merge queue Apr 30, 2026

Merged via the queue into main with commit 5c05a5b Apr 30, 2026
8 checks passed

avinash2692 deleted the avi/feat/granite4.1 branch April 30, 2026 16:49

nrfulton mentioned this pull request May 1, 2026

feat: update granite library examples to use Granite 4.1 3B adapters. #981

Merged

9 tasks

Conversation

avinash2692 commented Apr 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Misc PR

Type of PR

Description

Summary

What changed

What was NOT changed (intentional)

Testing

Attribution

Uh oh!

github-actions Bot commented Apr 29, 2026

Uh oh!

nrfulton left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

avinash2692 commented Apr 29, 2026

Uh oh!

ajbozarth left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ajbozarth commented Apr 29, 2026

Uh oh!

avinash2692 commented Apr 29, 2026

Uh oh!

avinash2692 commented Apr 29, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

avinash2692 commented Apr 29, 2026 •

edited

Loading