Skip to content

Release files: mark a release with the commit that added its file - #28

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

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

Conversation

@AlexKempen

Copy link
Copy Markdown
Member

The Fasteners v1.1.0 release from #27 never ran. fs run-releases stopped with "fasteners.toml already made Fasteners - v1.0.0" before making anything. The cause: the marker that ends each release's version descriptions was just the file name, [releases/fasteners.toml], and v1.0.0's release used the same name. Main itself landed in Onshape fine.

The marker now also names the commit that added the file: [releases/fasteners.toml ad9171e650a2].

  • A retry of the same file, after a run that stopped partway, still matches and stops.
  • A later file reusing a name is a new release.

The test checks both cases. docs/fs-cli.md describes the new marker.

uv run pytest -q: 943 passed.

Merging this runs the Onshape workflow again. releases/fasteners.toml is still pending on main, so the run makes Fasteners - v1.1.0 in the backend and rebuilds FRCDesignLib's Part Studios. FRCDesignLib's document is not versioned.


Generated by Claude Code

The marker ending a release's version descriptions was the file's name
alone, so a file reusing a released file's name, as releases/fasteners.toml
did for v1.1.0, was taken for the earlier release and stopped
fs run-releases before it made anything. It now names the commit that added
the file too: a retry of the same file is still found, and a later file of
the same name releases.

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