[segmentarr]: v1.5.2

[Tw1zT3d2four7]

About this submission

Pre-submission checklist

If this is a new plugin:

• Plugin folder is named lowercase-kebab-case
• plugin.json contains all required fields (name, version, description, author or maintainers, license)
• My GitHub username is in author or maintainers
• license is a valid OSI-approved SPDX identifier (e.g. MIT, Apache-2.0)
• I have tested the plugin against a running Dispatcharr instance

If this is an update to an existing plugin:

• version in plugin.json is incremented (unless this is a metadata-only change - see Versioning)
• I am listed in author or maintainers of the existing plugin

[Tw1zT3d2four7]

Hey, just giving this PR a quick bump. All validation checks are passing, and there are no conflicts with main.

Whenever you get a chance to review it, I’d appreciate it. Thanks!

[dispatcharr-plugins-bot]

Plugin Validation Results

Modified plugins: 1

Plugin: segmentarr

HLS-segmenting stream profile for Dispatcharr: splits XC/URL provider streams into segments, repairs timestamp breaks, and delivers clean MPEG-TS through cvlc to a matching Output Profile.

Source Repository

Check	Status	Details
Required fields	✅	All required fields present
Release artifact	✅	Artifact reachable at resolved URL
Maintainers	✅	Tw1zT3d2four7, Tw1zT3d2four7
License	✅	MIT - MIT License
Permission	✅	New plugin - Tw1zT3d2four7 listed in author/maintainers
Version	✅	1.5.2
Version bump	✅	New plugin

View release v1.5.2 on GitHub

---

🎉 All validation checks passed!

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

---

Other plugins by Tw1zT3d2four7 in this repository (2)

Plugin	Slug	Version
Decypharr VOD	decypharr-vod	1.0.7
Profilarr	profilarr	2.1.6

[sethwv]

Hey @Tw1zT3d2four7

Especially with new submissions to the repository, we need details in the pull request body rather than a blank template. This provides a starting point for review and confirms the content is suitable for distribution.

We have also observed that you sometimes to remove the previous tag or release when issuing a plugin update. If possible, avoid this practice, as it hinders our review and limits users’ ability to audit what they download during an update.

If you have any questions or concerns about this Please shoot me a dm @seth on Discord, or happy to answer any questions on this PR. Thanks for your continued submissions and willingness to work with us! :)