Skip to content

[could-not-dispatch] Update to 0.6.0 - #482

Merged
dispatcharr-plugins-bot[bot] merged 2 commits into
Dispatcharr:mainfrom
PilaScat:update-could-not-dispatch-0.6.0
Oct 25, 2026
Merged

dispatcharr-plugins-bot[bot] merged 2 commits into
Dispatcharr:mainfrom
PilaScat:update-could-not-dispatch-0.6.0

Conversation

@PilaScat

Copy link
Copy Markdown
Contributor

About this submission

Update of an existing external plugin, 0.5.1 → 0.6.0.

  • A second card for a channel that reached the fallback because the provider was full.
    With Image or video when the provider is full set and an API key, a channel whose every
    source belongs to a provider account that was at its connection limit in the last 20 seconds
    gets that card, so it can say that every connection is in use; every other channel gets the
    usual one. Each fallback stream now points at the card with its channel,
    slate.ts?channel=<uuid>, rewritten by the next Apply or Cover new channels. Only these two
    cases are told apart: Dispatcharr does not tell a plugin why each stream failed, so a broken
    link and a passing outage look the same
    (#1, from
    @ckegels).

  • A channel hidden from the output now goes back to its first stream like any other. The
    Dispatcharr channel list leaves hidden channels out unless asked, so such a channel stayed on
    the card until someone tuned away.

  • Source: https://github.com/PilaScat/could-not-dispatch

  • Release: https://github.com/PilaScat/could-not-dispatch/releases/tag/v0.6.0

  • Changelog: https://github.com/PilaScat/could-not-dispatch/blob/v0.6.0/CHANGELOG.md

  • Zip sha256: 097a6a6337a556bea054c63608267b3f0d17ec7e3bfea88dbc0088f43de2d89b

Opened by registry-pr.yml in PilaScat/could-not-dispatch when v0.6.0 was released.

Copilot AI balanced review requested due to automatic review settings October 25, 2026 00:06

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.

@dispatcharr-plugins-bot dispatcharr-plugins-bot Bot added the Plugin Update A plugin already in the repository is being updated. label Oct 25, 2026
@dispatcharr-plugins-bot

Copy link
Copy Markdown
Contributor

Plugin Validation Results

Modified plugins: 1

Plugin: could-not-dispatch

Plays a looping image or video when every real stream on a channel has failed, so viewers see a message instead of a black screen. With an API key, it later sends the channel back to its first stream.

Source Repository

Check Status Details
Required fields ✅ All required fields present
Release artifact ✅ Artifact reachable at resolved URL
Maintainers ✅ PilaScat
License ✅ MIT - MIT License
Permission ✅ You have permission to modify this plugin
Version ✅ 0.6.0
Version bump ✅ 0.5.1 → 0.6.0

View release v0.6.0 on GitHub · Compare v0.5.1...v0.6.0


🎉 All validation checks passed!

This PR modifies 1 plugin(s) and all checks have passed.


Other plugins by PilaScat in this repository (2)
Plugin Slug Version
Gluetun Rotate gluetun-rotate 0.4.0
Underfed underfed 0.9.0

@dispatcharr-plugins-bot
dispatcharr-plugins-bot Bot merged commit a137c8a into Dispatcharr:main Oct 25, 2026
12 checks passed
@dispatcharr-plugins-bot dispatcharr-plugins-bot Bot added the Auto Merged PR was merged automatically after validation label Oct 25, 2026
@PilaScat
PilaScat deleted the update-could-not-dispatch-0.6.0 branch October 25, 2026 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Auto Merged PR was merged automatically after validation Plugin Update A plugin already in the repository is being updated.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants