Skip to content

chore: pick up the current py-canon - #145

Merged
soodoku merged 2 commits into
masterfrom
fleet/propagate-py-canon
Aug 19, 2026
Merged

chore: pick up the current py-canon#145
soodoku merged 2 commits into
masterfrom
fleet/propagate-py-canon

Conversation

@soodoku

@soodoku soodoku commented Aug 19, 2026

Copy link
Copy Markdown
Member

Opened by tools/fleet-propagate.sh in gojiplus/py-canon.

The @v1 reusable workflows update themselves; these two layers do not:

  • uv.lock pins the commit py-canon@v1 resolved to, so docs keep
    building against an old py_canon.sphinx until the lock is refreshed.
  • copier update is what carries template changes -- scaffolding and the
    shared [tool.*] config -- into a repo that already exists. Nothing runs it
    on a schedule.

Nothing here was hand-written. If the result is wrong, the fix belongs in the
template rather than in this diff.

Opened by tools/fleet-propagate.sh in gojiplus/py-canon: a lock refresh for the
pinned py-canon commit, a `copier update` against the template at v1, or both.

Nothing here was hand-written. If the result is wrong, the fix belongs in the
template rather than in this diff.
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

The lock refresh IS the 1.1.0 propagation; v1.1.0's only template delta
(run-preen: true) is already set explicitly in this repo's shim, so the
record matches reality.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@soodoku
soodoku merged commit 0b3fb29 into master Aug 19, 2026
12 checks passed
@soodoku
soodoku deleted the fleet/propagate-py-canon branch August 19, 2026 11:32
soodoku added a commit that referenced this pull request Aug 20, 2026
* chore: pick up the current py-canon

Opened by tools/fleet-propagate.sh in gojiplus/py-canon: a lock refresh for the
pinned py-canon commit, a `copier update` against the template at v1, or both.

Nothing here was hand-written. If the result is wrong, the fix belongs in the
template rather than in this diff.

* Record the v1.1.0 template tag

The lock refresh IS the 1.1.0 propagation; v1.1.0's only template delta
(run-preen: true) is already set explicitly in this repo's shim, so the
record matches reality.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
soodoku added a commit that referenced this pull request Aug 20, 2026
* chore: pick up the current py-canon

Opened by tools/fleet-propagate.sh in gojiplus/py-canon: a lock refresh for the
pinned py-canon commit, a `copier update` against the template at v1, or both.

Nothing here was hand-written. If the result is wrong, the fix belongs in the
template rather than in this diff.

* Record the v1.1.0 template tag

The lock refresh IS the 1.1.0 propagation; v1.1.0's only template delta
(run-preen: true) is already set explicitly in this repo's shim, so the
record matches reality.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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.

1 participant