Skip to content

Advertise the Yutils feed in knownFeeds#33

Open
line0 wants to merge 1 commit into
mainfrom
advertise-yutils-feed
Open

Advertise the Yutils feed in knownFeeds#33
line0 wants to merge 1 commit into
mainfrom
advertise-yutils-feed

Conversation

@line0

@line0 line0 commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Advertises the Yutils feed added in TypesettingTools/Yutils#2, so DependencyControl officially trusts it.

Yutils has been distributed by bundling it with the Aegisub installer, because no feed offered it. TypesettingTools/Yutils#2 adds one, packaging the library as tstools.Yutils and declaring the bare Yutils name in provides.

Listing that feed in knownFeeds folds it into the officially trusted set, which is all it takes for ASSFoundation's existing requirement — {"moduleName": "Yutils", "optional": true}, bare and feed-less — to resolve to it through the provides alias. ASSFoundation needs no change.

The indirection is deliberate. Putting the feed URL directly into ASSFoundation's feed would expose a 0.4.0 feed to v0.6.x clients, which can't parse it — the same format-compatibility trap we just dug out of. Advertising it here means the URL only ever appears in feeds that v0.7.0+ clients read; the retired master feed is left untouched, so v0.6.x never learns it exists.

Merge order: land TypesettingTools/Yutils#2 and push its v1.0.0 tag before this change is published to the publish branch. Otherwise DependencyControl advertises a feed URL that 404s — not fatal, since feed discovery tolerates unloadable feeds and the ASSFoundation requirement is optional, but it causes pointless failed fetches.

🤖 Generated with Claude Code

Yutils is packaged for DependencyControl in TypesettingTools/Yutils#2 as
`tstools.Yutils`, which declares the bare `Yutils` name in `provides`.
Advertising its feed here folds it into the officially trusted set, so
ASSFoundation's existing feed-less `Yutils` requirement resolves to it
without ASSFoundation having to reference a 0.4.0 feed that v0.6.x clients
can't parse.

The retired `master` feed is deliberately left untouched, so only v0.7.0+
clients ever discover the feed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Test results — macos-latest ✅1060 · ubuntu-latest ✅1060 · windows-latest ✅1057

Summary

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
3180 3177 0 3 0 0 1m 50s

🎉 No failed tests in this run.

Github Test Reporter by CTRF 💚

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants