Repository navigation
Update the assistant plugin to v0.0.11 - #213
Closed
github-actions[bot] wants to merge 1 commit into
Closed
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
update-plugin/assistant
branch
from
October 25, 2026 06:42
9aa6a1c to
9288d05
Compare
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
update-plugin/assistant
branch
from
October 26, 2026 06:59
9288d05 to
99c1d44
Compare
github-actions
Bot
changed the title
Contributor
|
Closing so the release scan recreates this update with a signed commit (datum-cloud/infra#7969). |
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.
assistantis on v0.0.5 here; milo-os/assistant has published v0.0.11.Opened or updated by the daily upstream scan. A plugin's own repo normally pushes its release to this catalog; this runs regardless of whether that happened, so the catalog cannot drift unnoticed.
Checksums come from the release's
checksums.txtwhere it has one, and are computed from the archives where it does not. PR validation downloads every URI and verifies them again.