Skip to content

Fix/docker docs include - #28

Merged
morpheuslord merged 2 commits into
mainfrom
fix/docker-docs-include
Oct 9, 2026
Merged

morpheuslord merged 2 commits into
mainfrom
fix/docker-docs-include

Conversation

@morpheuslord

Copy link
Copy Markdown
Owner

docker release fix

pyproject.toml force-includes docs/DOCUMENTATION.md and
docs/INVENTORY_REFERENCE.md into the wheel (the MCP cloudg://docs
resources serve them), but the Dockerfile copied only DOCUMENTATION.md
into the build context, so hatchling failed with "Forced include not
found: /app/docs/INVENTORY_REFERENCE.md" and the 0.6.0 image was never
pushed. Copy both. Also removes the em dashes from the Dockerfile
comments.
Publishing a GitHub release still runs everything automatically: it
builds the release tag, takes the version from the tag, publishes to
PyPI and pushes the image as :<version> and :latest.

A manual run (Actions -> Publish -> Run workflow) now takes inputs:
- ref: tag, branch or commit to build
- version: version to stamp and publish (default: from a vX.Y.Z ref,
  else pyproject.toml)
- targets: all, pypi or docker
- tag_latest: also tag the image :latest
- extra_tags: more image tags, comma-separated

So a broken image build can be redone on its own, for example
ref=main, version=0.6.0, targets=docker, without touching PyPI. A plan
job resolves and validates every input once (inputs reach the shell
only through environment variables) and writes the plan to the run
summary. The image now carries the same stamped version as the wheel.

First-party actions are pinned to commit SHAs like the third-party
ones, and checkouts no longer persist the git credential; zizmor
reports no findings.
@morpheuslord
morpheuslord merged commit f408d8d into main Oct 9, 2026
4 of 5 checks passed
@morpheuslord
morpheuslord deleted the fix/docker-docs-include branch October 9, 2026 15:42
@codacy-production

Copy link
Copy Markdown
Contributor

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

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