Skip to content

fix: int8-static artifact publishes under its own id - #226

Merged
ronaldtse merged 1 commit into
mainfrom
fix/int8static-distinct-id
Sep 30, 2026
Merged

ronaldtse merged 1 commit into
mainfrom
fix/int8static-distinct-id

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

What

One-line fix, hot on the heels of #224: the int8-static artifact must publish under its own id.

publish_model.py derives the canonical published filename from the zip metadata's id + precision. With the base id, the static zip's canonical name becomes ara-diac-small-2.1-int8.zip — identical to the shipped dynamic-int8 asset — so publishing would clobber it (asset re-upload under the same name, models.yaml entry replaced: the dynamic variant would be gone).

The id now carries the variant inside the slug (ara-diac-small-int8static-2.1 → canonical ara-diac-small-int8static-2.1-int8.zip). Slug placement is forced by the schema: ids must end in major.minor. Fixture spec extended to pin the id contract.

Spec

test_static_zip_declares_int8_and_validates_strict now asserts id == fixture-int8static-1.0 alongside the strict-validation pass (the strict gate exercises the schema id rule itself — the first cut of this fix, fixture-1.0-int8static, was caught exactly there).

publish_model derives the canonical filename from metadata id+precision;
with the base id the static zip's canonical name is
ara-diac-small-2.1-int8.zip — identical to the shipped dynamic-int8
asset, so publishing would clobber it. The id now carries the variant
inside the slug (schema ids must end in major.minor):
ara-diac-small-int8static-2.1 -> canonical ...-int8.zip, distinct.
@ronaldtse
ronaldtse merged commit 8e75be6 into main Sep 30, 2026
11 checks 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.

1 participant