-
Weatherreporter v0.13.0
StableAll checks were successfulci/woodpecker/tag/release Pipeline was successfulreleased this
2026-08-29 17:38:41 +00:00 | 0 commits to main since this releaseWeatherreporter v0.13.0
This release upgrades Weatherreporter's generated-text integration through
PromptKit v0.9.0 and adds bounded structured-output repair, inherited domain
profiles, safer provider diagnostics, and repair provenance.Summary
Weatherreporter now permits one PromptKit-owned corrective generation when a
model returns invalid or explicitly empty structured output. Successful and
failed results report the actual correction count when validation completed,
and explicit prompt-debug capture can retain bounded provider failure details
without exposing them in ordinary output.The stable
weather-light,weather-balanced, andweather-deepprofiles now
inherit their execution targets from PromptKit's maintained catalog. PromptKit
v0.9.0 assembles that catalog from independently versioned OpenRouter and
Rakestrawhome modules while preserving Weatherreporter's existing effective
profile targets and configured-profile override behavior.Compatibility
The documented CLI, configuration fields, report IDs, report filenames,
Markdown outputs, and Distributor integration remain compatible with v0.12.0.
The four generated-text prompts advance to version2.1.0; an eligible failed
validation may therefore make one additional provider call, increasing latency
and usage for that execution.Comparison bundles advance from schema v1 to v2 so each completed validation
can recordrepairAttempts. Weatherreporter intentionally recognizes only the
current bundle version for guarded replacement. An existing v1 comparison
bundle cannot be replaced with--replaceby this release.Upgrade
No special action is required for ordinary generation, batch execution,
configuration, or notification. Operators who want to reuse the destination
of a v1 comparison bundle must first remove or relocate that old bundle, or
select a new--out-dir.Operators should account for the possibility of one additional model call
when output repair is needed. Existing configured standalone, inherited, and
endpoint-only profiles retain their documented precedence.Changes
- Upgraded PromptKit from v0.5.0 through v0.9.0 and adopted its maintained
profile inheritance, optional credential-source behavior, structured repair,
generation-error contract, and externally maintained provider catalogs. - Converted the three Weatherreporter domain profiles into minimal aliases of
maintained PromptKit profiles without changing their effective model ladder. - Added one corrective-generation allowance to all four embedded prompts and
exposed actual repair counts in generate, batch, and comparison summaries. - Migrated the comparison bundle contract
to v2 with strict repair-provenance validation and safe partial publication
after independent profile failures. - Added safe provider HTTP status to ordinary errors while confining provider
code, type, and message to explicit securefailure.jsondebug artifacts. - Strengthened offline coverage for local endpoint-only profiles, optional
credentials, concurrent comparison repair outcomes, and failure-debug
isolation. - Updated the PromptKit integration guide,
configuration reference, CLI reference, and
operations guide for the implemented contracts.
Downloads
- Upgraded PromptKit from v0.5.0 through v0.9.0 and adopted its maintained
-
Weatherreporter v0.11.0
StableAll checks were successfulci/woodpecker/tag/release Pipeline was successfulreleased this
2026-08-02 02:09:47 +00:00 | 119 commits to main since this releaseWeatherreporter v0.11.0
This release adds a configurable default publication directory for generated
weather reports.Summary
Operators can now set
output.directoryonce for both individual reports and
scheduled batches. Explicit--outand--out-dirdestinations continue to
take precedence, while installations that omit the setting retain the existing
current-directory behavior.Compatibility
This release is additive and compatible with
v0.10.1. Existing configuration
files, commands, report filenames, Promptkit behavior, and Distributor
notification behavior remain valid and unchanged.Upgrade
No special action is required. To use the new default destination, configure
output.directoryas described in the configuration
reference. Existing deployments may continue using the current
working directory or explicit CLI output flags.Changes
- Added strict configuration loading and validation for the optional
output.directoryfield. - Applied the configured directory consistently to
generateandrun, with
explicit CLI destinations retaining highest precedence. - Preserved relative-path handling, absolute result paths, atomic publication,
cancellation safety, and Distributor notification ordering. - Strengthened output preflight so existing non-directory paths, uninspectable
paths, and dangling symlink components fail before expensive report work. - Updated the CLI reference and operations
guide for the new destination-selection behavior.
Downloads
- Added strict configuration loading and validation for the optional
-
Weatherreporter v0.10.1
StableAll checks were successfulci/woodpecker/tag/release Pipeline was successfulreleased this
2026-08-02 00:36:54 +00:00 | 125 commits to main since this releaseWeatherreporter v0.10.1
This release repairs release validation after the
v0.10.0pipeline failed in
its privileged build container. Application behavior is unchanged from
v0.10.0.Summary
The unreadable-secret configuration test now verifies that its process is
actually subject to file permission bits before asserting that a mode-000
file cannot be read. This keeps the test meaningful for ordinary users while
allowing the release suite to run correctly in privileged containers.Compatibility
This patch release makes no changes to Weatherreporter's CLI, configuration,
report output, integrations, prompts, profiles, or operating behavior. It is
fully compatible withv0.10.0.Upgrade
No special operator action is required. Use
v0.10.1in place ofv0.10.0;
thev0.10.0tag remains immutable, but its failed pipeline did not publish
release binaries.Changes
- Made the unreadable-secret test capability-aware when the test process can
bypass filesystem permission bits. - Preserved the production contract that genuinely unreadable secret files
fail configuration loading. - Restored portable release validation in Woodpecker's privileged Go
container.
Downloads
- Made the unreadable-secret test capability-aware when the test process can