Describe the issue
The push-triggered contributor updater at commit 185f4e6 replaces the “Contributors” and “Developers” areas with one cross-section regular expression, normalizes the file ending, and then pushes to master. I rechecked the current branch before filing this issue; the README, updater script, and workflow blobs are unchanged from that tested commit. A boundary mistake can therefore affect both sections before the bot commit.
I reproduced a representative “Contributors” update with Texio 0.1.2. The explicit named-section operation preserved the following “Developers” section and all other bytes, while missing and duplicate headings stopped without writing. Would you accept a small workflow trial that keeps the current data collection and uv checks but previews and applies those two generated bodies separately?
Steps to Reproduce
The commands, pinned source, and hashes are in the Texio workflow pilot.
Expected behavior
The workflow updates only the two named bodies and refuses an ambiguous or missing heading before committing.
Actual behavior
The current regex spans both headings and writes the complete README result.
Screenshots
Not applicable; the linked pilot contains the reproducible commands and file hashes.
Environment details (please complete the following information):
- OS: macOS
- Version: 26.6.2
- Software version: Texio 0.1.2
Additional context
Texio is an MIT-licensed early preview that I maintain. A trial would add a pinned, checksum-verified binary download to the workflow. The tradeoff is installation time and a new CI binary in exchange for explicit section boundaries and fail-closed behavior.
Describe the issue
The push-triggered contributor updater at commit
185f4e6replaces the “Contributors” and “Developers” areas with one cross-section regular expression, normalizes the file ending, and then pushes tomaster. I rechecked the current branch before filing this issue; the README, updater script, and workflow blobs are unchanged from that tested commit. A boundary mistake can therefore affect both sections before the bot commit.I reproduced a representative “Contributors” update with Texio 0.1.2. The explicit named-section operation preserved the following “Developers” section and all other bytes, while missing and duplicate headings stopped without writing. Would you accept a small workflow trial that keeps the current data collection and
uvchecks but previews and applies those two generated bodies separately?Steps to Reproduce
The commands, pinned source, and hashes are in the Texio workflow pilot.
Expected behavior
The workflow updates only the two named bodies and refuses an ambiguous or missing heading before committing.
Actual behavior
The current regex spans both headings and writes the complete README result.
Screenshots
Not applicable; the linked pilot contains the reproducible commands and file hashes.
Environment details (please complete the following information):
Additional context
Texio is an MIT-licensed early preview that I maintain. A trial would add a pinned, checksum-verified binary download to the workflow. The tradeoff is installation time and a new CI binary in exchange for explicit section boundaries and fail-closed behavior.