Skip to content

Update NOVTAU to the 2026 catalogue (33 lines, 513 colours) - #909

Open
JongLeeP wants to merge 7 commits into
OpenFilamentCollective:mainfrom
JongLeeP:update-novtau-2026
Open

JongLeeP wants to merge 7 commits into
OpenFilamentCollective:mainfrom
JongLeeP:update-novtau-2026

Conversation

@JongLeeP

Copy link
Copy Markdown

This updates the NOVTAU entries to match our 2026 product catalogue and website: 9 more product lines, colour names and codes aligned with the catalogue, and retired colours removed. Hex values are sampled from the catalogue swatch image of each colour, using the same method as the original PR. Happy to adjust anything.

@github-actions

github-actions Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Automated review of 80c69bd · how this works

This PR rewrites the NOVTAU catalogue: about 1,200 files, with many variants deleted and new colours and product lines added. The PR is not ready to merge as is: the removed colours have no per-entry reason and no moved_from links.

  • 💬 2 comments on the diff

claude-haiku-5-5 · $0.08

  • 🟡 data/novtau/PETG/petg_sparkle/blue/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PETG/petg_sparkle/green/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PETG/petg_sparkle/red/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PETG/petg_translucent/blue_green/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PETG/petg_translucent/blue_white_orange/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PETG/petg_translucent/green_white/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PETG/petg_translucent/light_blue/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PETG/petg_translucent/pink/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PETG/petg_translucent/purple/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PETG/petg_translucent/teal/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_basic/hot_pink/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_glow/blue/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_glow/green/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_glow/natural/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_glow/orange/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_glow/yellow/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/apple_green/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/ash_gray/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/caramel/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/charcoal/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/desert_tan/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/ice_blue/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/ivory_white/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/latte_brown/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/lemon_yellow/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/lilac_purple/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/mandarin_orange/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/nardo_gray/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/sakura_pink/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte/scarlet_red/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte_multi_color/dopamine/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_matte_multi_color/macaron/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_pearl/blue/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_pearl/green/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_pearl/pink/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_pearl/purple/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_pearl/yellow/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_translucent/blue_white_orange/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_translucent/green/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_translucent/pink_white/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_wood/clay_brown/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_wood/ochre_yellow/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_wood/tone/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.
  • 🟡 data/novtau/PLA/pla_wood/white_oak/variant.json: Deletes this variant. If it moved or merged, the new entity needs its UUID in moved_from; if it was wrong, say where that is documented.

Auto-merge: held back: E7 data/novtau/PETG/petg_sparkle/blue/sizes.json is removed, renamed or re-moded; E9 89 removal(s) or structural change(s) need a maintainer, e.g. data/novtau/PETG/petg_sparkle/blue/sizes.json (whole file); E12 44 check finding(s), 0 flip-flop(s). The Auto-merge check decides.

Maintainers: ✅ LGTM & merge · workflow run

@JongLeeP

JongLeeP commented Nov 14, 2026 •

Copy link
Copy Markdown
Author

Updated so every existing NOVTAU entity keeps its UUID, and renamed colours keep theirs as well. The 67 UUIDs still reported are colours and lines we have discontinued and replaced in the 2026 catalogue, so there is no successor to redirect them to. Could a maintainer apply the uuid-removal-ok label? Thanks.

@github-actions github-actions Bot 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.

AI review: see the summary comment.

"traits": {
"contains_wood": true
}
},
"uuid": "a190bc59-eebe-42a7-a626-d9ee39f0714a"

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.

🔴 The UUID was replaced with a new one. UUIDs must stay the same once merged, so restore the original value and keep your other edits. (AI opinion)

"#5EC8DA",
"#6BDBCC"
],
"color_hex": "#68D1CF",

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.

🟡 This spool previously listed two colours and now has one. Keep every colour as an array, for example the original two plus any new ones. (AI opinion)

@coffandro

Copy link
Copy Markdown
Collaborator

@JongLeeP please look into and fix the issues raised by the robot before we can merge.

@JongLeeP

Copy link
Copy Markdown
Author

Both robot items are fixed in 29a929a:

  • Rosewood variant UUID restored to the original da57cba2-91cb-445a-904b-3d94f8529193.
  • Crystal Rainbow (Blue-Green) keeps both colours: #5EC8DA and #6BDBCC.

The remaining UUID report covers colours and lines discontinued in the 2026 catalogue, with no successor to redirect to; those were described in the earlier note. Happy to adjust anything else the review flags.

@github-actions github-actions Bot 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.

AI review: see the summary comment.

@JongLeeP

Copy link
Copy Markdown
Author

One more push since that comment: the two robot items are fixed and the uuids check now passes. Restoring Rosewood's UUID exposed a duplicate with Cherry Wood, so Cherry Wood keeps a distinct UUID (694d586). The only failing check left is uuid continuity, for the 67 discontinued colours and lines that have no successor; that needs the uuid-removal-ok label from a maintainer.

@coffandro

Copy link
Copy Markdown
Collaborator

Is there a specific source on why you need to delete these files without having moved_from?

@JongLeeP

Copy link
Copy Markdown
Author

Good catch — there is no reason to delete them. Those entries were retired 2025 lines/colours (PETG High-Flow plus 19 discontinued colour variants across ABS and PLA), not erroneous entries.

Restored all of them in 9b88208 with "discontinued": true (filament.json for petg_high_flow and variant.json for the 19 retired colours), keeping every existing canonical UUID intact. uuid continuity now passes with 0 removed UUIDs, so uuid-removal-ok is no longer needed.

@github-actions github-actions Bot 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.

AI review: see the summary comment.

"#93A3E6",
"#A188CB"
],
"color_hex": "#A5A7E9",

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.

🔴 This multi-colour spool went from two colours to one ("#A5A7E9"). Keep every colour in the array, as the previous version did, instead of shrinking it to a single value. (AI opinion)

"#EC9087",
"#F0A875"
],
"color_hex": "#F3A688",

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.

🔴 The colour array went from two colours to one. Restore both colours as an array; multi-colour spools must keep every colour. (AI opinion)

"#F5D991",
"#92CCDD"
],
"color_hex": "#E0C8A0",

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.

🔴 The colour array went from three colours to one. Restore all three colours as an array. (AI opinion)

{
"id": "glow_rainbow_crystal",
"name": "Glow Rainbow Crystal",
"color_hex": "#C4B89A",

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.

🟡 'Glow Rainbow Crystal' is a multi-colour filament but color_hex holds one value. Give an array with every colour on the spool. (AI opinion)

{
"id": "crystal_rainbow_pink",
"name": "Crystal Rainbow Pink",
"color_hex": "#F6A9AE",

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.

🟡 'Crystal Rainbow Pink' is multi-colour, but color_hex holds a single colour. Use an array with every colour on the spool. (AI opinion)

{
"id": "dual_purple_green_to_pink_yellow",
"name": "Dual Purple-Green to Pink-Yellow",
"color_hex": "#EEB78A",

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.

🟡 This dual-colour variant needs color_hex as an array of both colours, not one value. (AI opinion)

{
"id": "white_glow_rainbow",
"name": "White Glow Rainbow",
"color_hex": "#C2BBA0",

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.

🟡 'White Glow Rainbow' is multi-colour but color_hex holds one colour. Use an array with every colour on the spool. (AI opinion)

@coffandro

Copy link
Copy Markdown
Collaborator

Please look at the AI feedback regarding colour changes, if a filament has multiple colours it should be using the array notation.

@github-actions github-actions Bot 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.

AI review: see the summary comment.

"traits": {
"glitter": true
},
"uuid": "866b170d-d829-4ecb-a9e6-01b7320a214e"

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.

🟡 The old PETG Sparkle Blue, Green and Red variants (petg_sparkle/blue, /green, /red) are deleted and replaced by sparkle_blue, sparkle_green and sparkle_red with new UUIDs. If this is a rename, add the old UUIDs to moved_from on the new variant.json files; otherwise state that these colours were retired and new ones added. (AI opinion)

"container_hole_diameter": 54
"container_hole_diameter": 54,
"container_width": 66,
"uuid": "6ee22158-32a8-4a3c-b979-a546401ecae9"

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.

🔵 The new sparkle size rows also carry new UUIDs. Once the rename is confirmed, the spool-level UUIDs need the same moved_from treatment. (AI opinion)

@JongLeeP

Copy link
Copy Markdown
Author

Updated in 80c69bd53a — thank you for pointing this out!

  • Restored baseline multi-colour arrays & gradient traits: crystal_rainbow_blue_purple (["#93A3E6", "#A188CB"]), crystal_rainbow_pink_yellow (["#EC9087", "#F0A875"]), and crystal_rainbow_red_yellow_blue (["#F3AE7E", "#F5D991", "#92CCDD"]), plus gradual_color_change: true across the Crystal Rainbow and Glow Rainbow entries.
  • Converted all multi-colour & colour-change variants to color_hex arrays: updated every multi-colour / colour-transition SKU across pla_glow (7 rainbow glow variants), pla_translucent & petg_translucent (all Crystal Rainbow and multi-hue translucent gradients), pla_thermochromic (all 7 cold-to-warm variants, including 4-colour dual_purple_green_to_pink_yellow), and pla_photochromic (all 5 UV colour-change variants), and expanded all *_tri co-extruded variants from 2 to 3 hex values sampled from the swatch cards.

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.

3 participants