Skip to content

Release v1.10.1 - #11

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
release/v1.10.1
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
release/v1.10.1

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 3, 2026

Copy link
Copy Markdown

Merging this pull request tags v1.10.1 and creates its GitHub release.

CI waits for approval: open the Checks tab and click Approve workflows to run.

Fixed

  • Every generated project gets RELEASING.md, not only PyPI libraries, with the PyPI setup and publishing steps only where they apply. It covers the one-time setup (including a greyed-out Actions setting), each release, the manual path with gh release create, and an "If a step fails" section. That section lists every refusal, says which ones a re-run clears, and explains why a failed publish needs a new release when the fix is in the repo. A project that deleted its RELEASING.md doesn't get it back from copier update.
  • The fragment template says Prepare release collects fragments. Every copier update command in the docs has --trust. The README lists all the workflows v1 delivers, describes the reusable workflows' permissions correctly, and its bump-v1 recovery command passes -R.
  • The CHANGELOG preamble and bump-v1.yml explain release-tag annotation correctly. Copier reads the version through dunamai, which takes the commit's newest tag by date and breaks a tie by name, so two lightweight tags give v1. It doesn't use git describe. bump-v1 annotates every release, since Release on merge creates the tag lightweight.

@MattFisher MattFisher closed this Oct 7, 2026
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