Skip to content

Bump the dotnet-dependencies group with 3 updates#5

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/src/dotnet-dependencies-c7b6184487
Closed

Bump the dotnet-dependencies group with 3 updates#5
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/src/dotnet-dependencies-c7b6184487

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 25, 2026

Copy link
Copy Markdown

Updated M3Undle.Core from 1.0.0-alpha.6 to 1.0.0-beta.1.

Release notes

Sourced from M3Undle.Core's releases.

1.0.0-beta.1

[v1.0.0-beta.1] — 2026-06-16

Beta 1 is the first beta release following Alpha 7. It fixes two playback bugs that broke HLS-sourced channels for every client, refines the adaptive stream recovery introduced in Alpha 7 to stop a class of channels from retuning far more than necessary, and makes provider onboarding faster and more resilient for large or slow catalogs.

HLS playback

Two separate issues combined to break every HLS-sourced channel (iptv-org, Samsung FAST, PBS, and similar), then persisted as an Electron-only failure after the first was fixed.

  • Fixed HLS channels producing no video at all. An HTTP reconnect setting meant for continuous streams was being applied to HLS as well, where every playlist and segment fetch ends in a normal end-of-file; M3Undle treated each one as a failure and looped on the playlist instead of advancing through it
  • Fixed Electron-based players, such as IPTVnator, failing once the above was fixed. They were being redirected to a generated HLS stream meant for browsers instead of receiving the raw MPEG-TS stream their player pipeline expects

Adaptive stream recovery

  • Fixed a stream-health tracking bug that caused some noisy channels to retune far more often than necessary — one channel that the recovery engine was already handling correctly still retuned 20 times in under three hours. Fixes #​96
  • Auto relay policy now also selects clean relay for Cautious channels, not just Unstable, catching more problem channels before they need a hard retune

Provider onboarding

  • Fixed slow or very large providers timing out before they finished loading. Providers now only time out when no data is being received rather than on total elapsed time, so large catalogs complete instead of failing. Fixes #​105
  • Series catalogs for Xtream providers now load in the background after a provider is added, making the initial add noticeably faster for large catalogs

Channel mapping

  • Fixed a provider group named "undefined" causing channels to disappear from the mapping page entirely instead of just showing as unmapped — affected iptv-org and similar providers
  • Fixed a malformed M3U entry swallowing the channel listed after it, silently dropping that channel from the lineup. Fixes #​107

Dashboard

  • Added a copy link for the Xtream endpoint URL to match the other published endpoint URLs. Fixes #​104

Docker and health

  • Fixed a newly deployed, not-yet-configured container reporting itself unhealthy to Docker; the dedicated health endpoint still correctly reports degraded until setup is complete, so monitoring isn't fooled, but compose no longer errors out on first boot. Fixes #​103
  • Fixed HDHomeRun tuner count defaulting to 1 when tuner count isn't tied to stream tracking

Container images

ghcr.io/sydney-elvis/m3undle:v1.0.0-beta.1
ghcr.io/sydney-elvis/m3undle:beta

1.0.0-alpha.7

[v1.0.0-alpha.7] — 2026-06-05

Alpha 7 is the final alpha milestone. It delivers adaptive live stream recovery for noisy provider channels, a first-class relay policy per provider, significant interface polish across nearly every page, and the consolidated schema migration that closes out all alpha database changes. Beta testing begins after this release.

Adaptive stream recovery

M3Undle now tracks per-channel stream health across sessions and uses that history to make smarter relay decisions.

  • Channels are classified as Stable, Cautious, or Unstable based on observed disconnect and reconnect events
  • Health classification persists in the database — it survives restarts and informs the next session startup
  • Clean-watch duration is tracked after the last adverse event; a channel relaxes one health level after 30 minutes of clean playback
  • At session startup, channel health is loaded before the first upstream connection so the relay decision is already informed before a single byte arrives
  • When clean recovery from an MPEG-TS/H.264 boundary is not safe, M3Undle issues a hard controlled retune instead of continuing with corrupt data
  • Cooldown policy improved to be less aggressive and avoid thrash after a single bad event

Provider relay policy

Replaced the hidden per-provider "clean remux" toggle with an explicit, user-facing Relay policy setting.

  • Auto — M3Undle decides: direct relay for Stable and Cautious channels, clean relay when channel health is Unstable
  • On — always use clean relay regardless of health
  • Off — always use direct relay regardless of health

Existing providers migrate automatically: prior off rows become Auto, prior legacy remux rows become On.

The relay policy, startup health classification, and relay decision reason are now visible on the stream monitor for every active session.

Stream monitor improvements

  • Transfer rates (bytes/sec) displayed per session and per connected client
  • Startup health and relay decision reason shown for each active session
  • Sessions display more detailed subscriber information

Retune compatibility fix

A controlled downstream retune is now suppressed when an internal or Generated HLS relay subscriber is attached to the shared session. A Jellyfin or NextPVR retune no longer kills a concurrent IPTVnator or browser HLS stream that is still active.

HDHomeRun page

New dedicated HDHomeRun page showing device identity, discovery endpoint, tuning endpoint, and configured tuner count. Makes manual client setup straightforward without hunting through settings.

About page

New About page with application version, build date, and project links. Fixes #​97.

Dashboard and navigation

  • Dashboard reorganized: active profiles are the primary focus, all published endpoint URLs grouped in one place
  • Always-on side drawer for fast navigation between pages without reopening a menu
  • Navigation highlights the currently active page
    ... (truncated)

Commits viewable in compare view.

Updated M3Undle.Core from 1.0.0-alpha.6-dev.1 to 1.0.0-beta.1.

Release notes

Sourced from M3Undle.Core's releases.

1.0.0-beta.1

[v1.0.0-beta.1] — 2026-06-16

Beta 1 is the first beta release following Alpha 7. It fixes two playback bugs that broke HLS-sourced channels for every client, refines the adaptive stream recovery introduced in Alpha 7 to stop a class of channels from retuning far more than necessary, and makes provider onboarding faster and more resilient for large or slow catalogs.

HLS playback

Two separate issues combined to break every HLS-sourced channel (iptv-org, Samsung FAST, PBS, and similar), then persisted as an Electron-only failure after the first was fixed.

  • Fixed HLS channels producing no video at all. An HTTP reconnect setting meant for continuous streams was being applied to HLS as well, where every playlist and segment fetch ends in a normal end-of-file; M3Undle treated each one as a failure and looped on the playlist instead of advancing through it
  • Fixed Electron-based players, such as IPTVnator, failing once the above was fixed. They were being redirected to a generated HLS stream meant for browsers instead of receiving the raw MPEG-TS stream their player pipeline expects

Adaptive stream recovery

  • Fixed a stream-health tracking bug that caused some noisy channels to retune far more often than necessary — one channel that the recovery engine was already handling correctly still retuned 20 times in under three hours. Fixes #​96
  • Auto relay policy now also selects clean relay for Cautious channels, not just Unstable, catching more problem channels before they need a hard retune

Provider onboarding

  • Fixed slow or very large providers timing out before they finished loading. Providers now only time out when no data is being received rather than on total elapsed time, so large catalogs complete instead of failing. Fixes #​105
  • Series catalogs for Xtream providers now load in the background after a provider is added, making the initial add noticeably faster for large catalogs

Channel mapping

  • Fixed a provider group named "undefined" causing channels to disappear from the mapping page entirely instead of just showing as unmapped — affected iptv-org and similar providers
  • Fixed a malformed M3U entry swallowing the channel listed after it, silently dropping that channel from the lineup. Fixes #​107

Dashboard

  • Added a copy link for the Xtream endpoint URL to match the other published endpoint URLs. Fixes #​104

Docker and health

  • Fixed a newly deployed, not-yet-configured container reporting itself unhealthy to Docker; the dedicated health endpoint still correctly reports degraded until setup is complete, so monitoring isn't fooled, but compose no longer errors out on first boot. Fixes #​103
  • Fixed HDHomeRun tuner count defaulting to 1 when tuner count isn't tied to stream tracking

Container images

ghcr.io/sydney-elvis/m3undle:v1.0.0-beta.1
ghcr.io/sydney-elvis/m3undle:beta

Commits viewable in compare view.

Updated MSTest from 4.2.2 to 4.2.3.

Release notes

Sourced from MSTest's releases.

4.2.3

See the release notes here

Commits viewable in compare view.

Updated Spectre.Console from 0.55.2 to 0.57.1.

Release notes

Sourced from Spectre.Console's releases.

0.57.1

What's Changed

  • GH2153: Fix async stack traces rendering as MoveNext() instead of source methods by @​devlead in #​2154

Full Changelog: spectreconsole/spectre.console@0.57.0...0.57.1

0.57.0

What's Changed

Full Changelog: spectreconsole/spectre.console@0.56.0...0.57.0

0.56.0

What's Changed

New Contributors

Full Changelog: spectreconsole/spectre.console@0.55.2...0.56.0

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps M3Undle.Core to 1.0.0-beta.1
Bumps MSTest from 4.2.2 to 4.2.3
Bumps Spectre.Console from 0.55.2 to 0.57.1

---
updated-dependencies:
- dependency-name: M3Undle.Core
  dependency-version: 1.0.0-beta.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: M3Undle.Core
  dependency-version: 1.0.0-beta.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: MSTest
  dependency-version: 4.2.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: Spectre.Console
  dependency-version: 0.57.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Jun 25, 2026
@dependabot @github

dependabot Bot commented on behalf of github Jul 2, 2026

Copy link
Copy Markdown
Author

Superseded by #6.

@dependabot dependabot Bot closed this Jul 2, 2026
@dependabot
dependabot Bot deleted the dependabot/nuget/src/dotnet-dependencies-c7b6184487 branch July 2, 2026 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants