d16fb6874c
Bring the release branch content onto the protected main line as a linear commit so the 0.3.0 release can be published without carrying dev merge history into main.\n\nConstraint: main requires pull-request updates and rejects force-pushes and merge commits.\nRejected: force-pushing main to v0.3.0 | blocked by repository rules and would bypass the protected release lane.\nConfidence: high\nScope-risk: broad\nDirective: Move or recreate the v0.3.0 tag only after this branch lands on main, then rerun the release asset workflow for the final main commit.\nTested: draft release assets and local artifact checks completed before this sync branch.\nNot-tested: full CI for the new PR branch has not completed yet.
2 lines
73 B
Python
2 lines
73 B
Python
"""Repository-local helper scripts used by tests and smoke harnesses."""
|