fix(http-canonicalization): bump to 0.16.2 to fix duplicate Alloy load [skip chg] - #11456
Open
timotheeguerin wants to merge 2 commits into
Open
fix(http-canonicalization): bump to 0.16.2 to fix duplicate Alloy load [skip chg]#11456timotheeguerin wants to merge 2 commits into
timotheeguerin wants to merge 2 commits into
Conversation
Contributor
|
❌ There is undocummented changes. Run The following packages have changes but are not documented.
Show changes |
…rk/alloy version [skip chg]
The published http-canonicalization@0.16.1 still required @typespec/emitter-framework@^0.17.0 (Alloy 0.22) while everything else moved to emitter-framework@0.19 (Alloy 0.24). npm installs of @typespec/http-server-csharp therefore loaded two incompatible @alloy-js/core copies ("Multiple versions of Alloy are loaded").
Manually bump the version and changelog to force a patched 0.16.2 stable release whose emitter-framework dependency is realigned, resolving the conflict for existing ^0.16.1 consumers.
Fixes #11443
timotheeguerin
force-pushed
the
fix/http-canonicalization-alloy-version
branch
from
July 29, 2026 19:36
92f32c3 to
1166a2e
Compare
timotheeguerin
changed the title
commit: |
|
You can try these changes here
|
timotheeguerin
marked this pull request as ready for review
July 29, 2026 22:54
timotheeguerin
requested review from
catalinaperalta,
iscai-msft,
markcowl and
xirzec
as code owners
July 29, 2026 22:54
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
1 participant
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.
Fixes #11443
Problem
Compiling a project that uses
@typespec/http-server-csharpwith npm fails at load time with:Two incompatible
@alloy-js/corecopies get installed and both load:0.24.1(hoisted) and0.22.0(nested under@typespec/http-canonicalization).Root cause
@typespec/http-server-csharp@0.58.0-alpha.30depends on@typespec/emitter-framework@^0.19.0(Alloy0.24) and@typespec/http-canonicalization@^0.16.1.^0.16.1resolves to the stale stable@typespec/http-canonicalization@0.16.1, whose published deps still require@typespec/emitter-framework@^0.17.0(Alloy0.22).^0.22.0peer → a second nested@alloy-js/core@0.22.0→ Alloy's runtime guard throws.Why the stable range went stale (a chronus bug)
@typespec/emitter-frameworkreceived minor bumps0.17 → 0.18 → 0.19(Alloy peer^0.22 → ^0.24).@typespec/http-canonicalizationdepends on it viaworkspace:^, but chronus 1.3.1 did not forceworkspace:^dependents to re-release on a minor bump of a0.xdependency (for0.x,^0.n.xlocks the minor, so a minor bump is effectively breaking). As a resulthttp-canonicalization's stablelateststayed frozen at0.16.1with the old^0.17.0range.This was fixed upstream in chronus 1.4.0 (timotheeguerin/chronus#590), which is already adopted here, so it won't recur.
Fix
Manually bump
@typespec/http-canonicalizationto 0.16.2 and add the changelog entry ([skip chg]) to force a targeted patched re-release. On publish itsworkspace:^emitter-framework dependency is resolved to the current line (Alloy0.24), so a single Alloy version is required across the tree.Patch (not minor) is deliberate:
http-server-csharp@0.58.0-alpha.30requests^0.16.1(>=0.16.1 <0.17.0), so0.16.2is picked up automatically and retroactively fixes already-published consumers;0.17.0would not satisfy that range.