Skip to content

The 0.3.0 release - #40

Merged
fabeat merged 1 commit into
mainfrom
release/0.3.0
Oct 30, 2026
Merged

fabeat merged 1 commit into
mainfrom
release/0.3.0

Conversation

@fabeat

@fabeat fabeat commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

The changelog gains the heading the release job reads, and the link reference at the bottom.

released="$(sed -n 's/^## \[\([^]]*\)\].*/\1/p' CHANGELOG.md | grep -v '^Unreleased$' | head -1)"
# → 0.3.0

What is in it

Added — a theme named in code, outranking the deck's own; a deck that comes back as bytes; the furniture of a deck written once, as a template; the slide templates; the FileFinder, so the files a deck names can come from somewhere the caller chooses.

Changed — ThemeLoader::load() and loadManifest() take a ?FileFinder where they took a ?PathScope, and their first parameter is now a theme's name rather than its directory; ThemeResolver's loader parameter became nullable; PresentationRenderer::__construct() gained a trailing named parameter; four public parameters were renamed from $files to $scope; LoadedTheme::template() returns a Master rather than a path.

Added, for the reader of the install instructions — the README now names cweagans/composer-patches where the requirement is stated, says what happens without it, and lists the five fixes the patch adds and which direction needs each.

What is left

The tag, which is a person's to make:

git tag -a v0.3.0 -m v0.3.0
git push origin refs/tags/v0.3.0

The tag is what triggers the release. Packagist reads the tag rather than the release, and it does not read it the moment the tag is pushed.

This release carries a breaking change. A consumer that called ThemeLoader::load() with a directory has to pass a name and a finder; the changelog says so, under Changed.

The changelog gains the heading the release job reads, and the link reference at the bottom.
@sonarqubecloud

Copy link
Copy Markdown

@fabeat
fabeat merged commit a73717e into main Oct 30, 2026
8 checks passed
@fabeat
fabeat deleted the release/0.3.0 branch October 30, 2026 15:22
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