Repository navigation
release: verwalter 0.31.0 - #103
Merged
Merged
Conversation
verwalter-release
Bot
force-pushed
the
release/main
branch
8 times, most recently
from
November 19, 2026 10:31
3670d53 to
838b935
Compare
verwalter-release
Bot
force-pushed
the
release/main
branch
from
November 19, 2026 10:36
838b935 to
7ebdaa2
Compare
lukasIO
approved these changes
Nov 19, 2026
This branch was successfully deployed
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.
Merging this PR releases:
verwalter
0.30.0→0.31.0Minor Changes
publishfails a package whose files changed since its tag, before its publish command runs. The reason namesref=<tag>: a run by hand from a later commit no longer publishes newer source under the tagged version.publish --allow-changed-sourceturns the check off. Versions the registry has are skipped before the check. - #105 (@lukasIO)releaserefuses to attach or upload assets for a tag from an earlier run when the package's files changed since the tag, and namesref=<tag>. A release without assets is still created.release --allow-changed-sourceturns the check off. - #109 (@lukasIO)release.required_assetson a package lists the asset names its GitHub release must have:release --publishandpublishleave the release a draft and fail while one is missing.publishthen does not run the publish command. - #110 (@lukasIO)status --check [--package <name>]exits non-zero when the current version of a package is not completely released: a tag that is not on the remote, a missing or draft GitHub release, a missing required asset, or a version the registry does not have. - #111 (@lukasIO)status --jsonprints the status of every package as one JSON list, for a tool that reads it - #118 (@lukasIO)Patch Changes
webrtc-sys/buildinsidewebrtc-sys, counts as a change of that package only. Before, the changeset check also required a changeset for the package around it. - #101 (@lukasIO)Changesets:
automatic_config_discovery.md,nested-package-check.md,publish-checks-tagged-source.md,release-checks-tagged-source.md,required-assets.md,status-check.md,status-json.md