ci: fix release-please output keys; allow tag rebuilds - #44
Merged
Conversation
In manifest mode release-please emits per-package outputs (app--tag_name) plus a top-level releases_created, not the bare release_created/tag_name the build gate read — so v0.2.0 got tagged but the build was skipped. Read the correct keys, and add a workflow_dispatch `tag` input that checks out and builds an existing tag so its assets (bundles + latest.json) can be filled in.
release-please re-serializes CHANGELOG.md and tauri.conf.json its own way on every release (expanded JSON arrays, double-spaced changelog headers), which oxfmt then flags — failing CI on each release commit. Add both to the fmt/lint ignorePatterns so the two tools stop fighting.
ApocDev
force-pushed
the
ci/fix-release-outputs
branch
from
June 30, 2026 18:35
b619c23 to
18fe3dd
Compare
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
1 participant
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.
v0.2.0 got tagged but the build was skipped — in manifest mode release-please emits per-package outputs (
app--tag_name) and a top-levelreleases_created, not the barerelease_created/tag_namethe build gate read.releases_createdgate,app--tag_nametag).workflow_dispatchtaginput that checks out + builds an existing tag, so a release missing its assets (v0.2.0) can be filled in.After merge: dispatch with
tag=v0.2.0to populate v0.2.0's bundles +latest.json; future releases build automatically.