Skip to content

Tag a part set's releases by the set's name - #26

Merged
AlexKempen merged 1 commit into
mainfrom
claude/zealous-shannon-e0iklk
Nov 8, 2026
Merged

AlexKempen merged 1 commit into
mainfrom
claude/zealous-shannon-e0iklk

Conversation

@AlexKempen

Copy link
Copy Markdown
Member

A part set's release tag was named after the released Feature Studio's file. FRC's and FTC's fasteners share fasteners.fs, so the FTC release found fasteners/v1.0.0 already there and went untagged.

The release now names its tag after the part set (ftcFasteners/v1.0.0). FRC's set is called fasteners, so its tags keep their names. A new test releases two sets that share a FeatureScript and checks that each gets its own tag. It fails with the old naming.

The missing ftcFasteners/v1.0.0 tag belongs on 9c51487, main's newest commit when the FTC release ran. It has to be pushed by hand: git tag -a ftcFasteners/v1.0.0 9c51487 -m "FTC Fasteners - v1.0.0" && git push origin ftcFasteners/v1.0.0.

uv run pytest -q: 943 passed. Merging runs the Onshape workflow, which lands main in Onshape. No releases are pending, so it releases nothing.


Generated by Claude Code

Tags were named for the released FeatureScript's file, which FRC's and FTC's
fasteners share, so FTC's release found fasteners/v1.0.0 already there and
went untagged. A part set's are now named for the set (ftcFasteners/v1.0.0);
FRC's set is named fasteners, so its tags keep their names.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T4daFKz4qvNwCEYcg38VKS
@AlexKempen
AlexKempen merged commit b55b478 into main Nov 8, 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