Repository navigation
Prepare release 0.1.0 - #13
Merged
Merged
Conversation
Date the changelog section for 0.1.0 and open a new Unreleased one. Add the per-slide style overrides, which shipped without an entry, and word the Content-Security-Policy entry for a first release. The README and the demo deck's getting-started slide now install from PyPI, which is true once 0.1.0 is published. The README keeps the repository install for changes that aren't released yet.
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
All reviewed documentation and changelog changes are complete with no unresolved issues.
Review effort: Lite
Findings: None
What changed in this PR
Prepares Akceo’s initial 0.1.0 PyPI release.
Changes:
- Adds PyPI and pipx installation guidance.
- Updates the demo deck installation command.
- Adds the dated
0.1.0changelog entry.
| File | Description |
|---|---|
README.md |
Documents PyPI and repository installation options. |
examples/demo/deck.md |
Uses the PyPI installation command. |
CHANGELOG.md |
Adds the 0.1.0 release notes. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the first release. Merging this doesn't publish anything; the
v0.1.0tag does, and it's pushed separately after merge.What changes
CHANGELOG.md: the section is now## [0.1.0] - 2026-09-24, with a new emptyUnreleasedabove it. It adds the per-slide style overrides (style-h1…style-sub), which shipped without an entry. The Content-Security-Policy entry is reworded for a first release ("doesn't load" rather than "no longer loads").README.md: installs from PyPI (uv tool install akceoorpipx install akceo). The repository install is kept for changes that aren't released yet.examples/demo/deck.md: the getting-started slide installs from PyPI.The version in
pyproject.tomlwas already0.1.0.Checked before tagging
v0.1.0: the heading check passes, and the notes extraction returns the 0.1.0 section (37 lines).akceo --versionprintsakceo 0.1.0, andcheck,buildandthemeswork on the demo deck.uv run pytest(168 passed), ruff,ruff format --checkand pyright.After merge
Tag
v0.1.0frommain. The release workflow tests on 3.12–3.14, builds, publishes to PyPI and creates the GitHub Release. The changelog date has to be within a day of the tag, so a tag later than 2026-09-25 needs the date moved first.