Skip to content

build: Bump AlphaSkia.Native.Windows and 7 others - #442

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/apps/bandroom/windows/minor-and-patch-2b8f0afb85
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/apps/bandroom/windows/minor-and-patch-2b8f0afb85

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.


Updated AlphaSkia.Native.Windows from 3.4.135 to 3.5.147.

Release notes

Sourced from AlphaSkia.Native.Windows's releases.

3.5.147

What's Changed

Full Changelog: CoderLine/alphaSkia@v3.4.135...v3.5.147

Commits viewable in compare view.

Pinned AlphaTab at 1.9.0.

Release notes

Sourced from AlphaTab's releases.

1.9.0

See https://alphatab.net/docs/releases/release1_9 for a detailed overview and description of the new features in this release.

What's Changed

Commits viewable in compare view.

Updated Microsoft.NET.Test.Sdk from 18.11.0 to 18.12.0.

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

18.12.0

Security fix

This release includes the fix for CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged executionComplete.json written by another local user, and then run attacker-controlled output handling.

Affected: Microsoft.TestPlatform.CLI 18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.

Microsoft.TestPlatform.CLI is the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.

The fix is also released in the Microsoft.TestPlatform.CLI package, for completeness. That package is rarely used directly. It is not a dependency of Microsoft.NET.Test.Sdk or Microsoft.TestPlatform, so those packages do not bring it in.

Details: microsoft/vstest#16654 and dotnet/announcements#517

Using custom Docker images or Nano Server? See microsoft/vstest#16652

What's Changed

Full Changelog: microsoft/vstest@v18.11.0...v18.12.0

18.11.1

Security fix

This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged executionComplete.json written by another local user, and then run attacker-controlled output handling.

Affected: Microsoft.TestPlatform.CLI 18.11.0.
Fixed in: Microsoft.TestPlatform.CLI 18.11.1.

Microsoft.TestPlatform.CLI is the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.

The fix is also released in the Microsoft.TestPlatform.CLI package, for completeness. That package is rarely used directly. It is not a dependency of Microsoft.NET.Test.Sdk or Microsoft.TestPlatform, so those packages do not bring it in.

Details: microsoft/vstest#16654 and dotnet/announcements#517

Using custom Docker images or Nano Server? See microsoft/vstest#16652

What's Changed

Full Changelog: microsoft/vstest@v18.11.0...v18.11.1

Commits viewable in compare view.

Updated Microsoft.Windows.SDK.BuildTools from 10.0.28000.2705 to 10.0.28000.2957.

Updated Microsoft.WindowsAppSDK from 2.5.1 to 2.6.5.

Release notes

Sourced from Microsoft.WindowsAppSDK's releases.

2.6.5

Windows App SDK 2.6.5 delivers targeted fixes for rendering, window composition, system backdrops, and packaged app installation.

Bug fixes

Bug fix Runtime Compatibility Change
Fixed rendering corruption that could occur on systems with multiple graphics adapters or monitors. N/A, rendering-region fix
Fixed an E_NOINTERFACE crash when enabling the System Composition Engine on Windows builds that lack the required interfaces. The runtime now uses the lifted compositor on those builds. N/A, operating system capability detection fix
Fixed an issue where window backgrounds and GDI controls could become unexpectedly transparent on Windows 10, including apps hosting XAML islands. N/A, window composition ABI fix
Reverted the system backdrop change introduced in 2.6.4 to address wrong-thread exceptions. System backdrops for content islands and XAML windows are not supported when using the System Composition Engine in this release. N/A, revert of a previously contained change
Fixed an issue where app-extension registration metadata generation returned E_NOTIMPL, which could prevent packaged apps from installing. N/A, missing implementation fix

For details, see the full Windows App SDK 2.6.5 release notes.

Try it out

Getting started

To get started using Windows App SDK to develop Windows apps, check out the following documentation:

2.6.4

Windows App SDK 2.6.4 removes the Limited Access Feature requirement for the Language Model APIs, updates ONNX Runtime to 1.27.1, and includes reliability fixes across WinUI 3, app lifecycle, notifications, DispatcherQueue, Content, composition, and Windows AI.

What's new in WinAppSDK 2.6.4:

  • Language Model APIs no longer require a Limited Access Feature unlock. Apps can call the Language Model APIs without first unlocking the Language Model Limited Access Feature. Apps using earlier Windows App SDK versions must continue to follow the LAF requirements for their target Windows versions.
  • Updated ONNX Runtime. The version of ONNX Runtime has been updated to 1.27.1. See ONNX Runtime versions for more info.

Bug fixes:

Bug Fix Runtime Compatibility Change
Fixed an access violation crash that could occur during app shutdown when a text control, such as a TextBox or RichEditBox, was still alive while the XAML core was being torn down. CCoreServices_InputServicesTeardownOrder
Fixed an issue where AppInstance.GetInstances could fail with E_INVALIDARG while enumerating application instances. AppLifecycle_GetInstancesProcessHandleFix
Fixed a crash when calling some AppNotificationManager and AppInstance APIs. AppNotification_AppInstance_FixStackOverflowCrash
Fixed an issue where self-contained apps could fail to load Microsoft.WindowsAppRuntime.Insights.Resource.dll when using the VersionInfo APIs or registering an AppNotification callback (microsoft/WindowsAppSDK#​6071, microsoft/WindowsAppSDK#​6387). VersionInfo_MissingInsightsResourceDll
Fixed an issue where an unhandled exception in a DispatcherQueue callback could produce a crash dump with only the HRESULT, omitting the app's original exception type, message, and stack trace. DispatcherQueue_CaptureCallbackErrorContext
Fixed the same crash dump issue for unhandled exceptions in DispatcherQueueTimer.Tick event handlers. DispatcherQueueTimer_CaptureTickErrorContext
Fixed an issue where a failure while creating a ContentIsland or other Content object immediately terminated the app. The original error is now returned to the calling code instead. ContentIsland_InitializationFailureCleanup
Fixed system backdrop support for lifted content islands and XAML windows when using the System Composition Engine. SwitcherSystemBackdropBrushSupport
Fixed projection of compatible Windows.UI.Composition objects into Microsoft.UI.Composition, preserving object identity, when using the System Composition Engine. SwitcherColdWrappingWUCToMUC
Fixed a crash in ItemsView when the target of StartBringItemIntoView was collapsed or recycled before the scroll completed (microsoft/microsoft-ui-xaml#​11865). ItemsView_InvalidBringIntoViewAnchor
Fixed a crash that could occur when a WebView2 control received focus while still initializing and its parent window was temporarily disabled when initialization finished. WebView2_HandleMoveFocusInvalidArgument
Improved diagnosability for Windows AI model initialization APIs. AIFabric_Tip_APIClassName_ReasonName
Fixed false IntelliSense errors on XAML-generated members, such as InitializeComponent and x:Name fields, in WinUI 3 C# projects edited in VS Code with C# Dev Kit. To opt out, set the EnableWinUIDesignTimeGeneratedXamlCompileItems property to false. N/A, build .targets change

To see everything that's new and changed, see the full Windows App SDK 2.6.4 release notes.

Try it out

  • Download the 2.6.4 NuGet package to use WinAppSDK 2.6 in your app.
  • Download and update the WinUI Gallery to see the WinUI 3 updates firsthand.

Getting started

To get started using Windows App SDK to develop Windows apps, check out the following documentation:

2.5.4-exp

Windows App SDK 2.5 Experimental is the latest experimental release, adding new Windows AI capabilities, code-based theme resource bindings and DataTemplate construction, the new TableView and Chart controls, and expanded WinUI 3 inking support. It follows Windows App SDK 2.5.1 stable and brings forward the changes from that release alongside the experimental-only additions below.

What's new in WinAppSDK 2.5 Experimental:

  • Windows AI device selection. New AIComputeDevice APIs let apps choose the default, CPU, or NPU execution device for text recognition. App Content Index image indexing can use the same preference for OCR through ContentRegionImageOptions.PreferredTextRecognizerDevice.
  • AI Speech and language model updates. New speech recognition factories improve model configuration and creation, while updated audio, streaming, and continuous recognition APIs expand speech scenarios. Language model APIs now expose model identity, low-rank adapter compatibility, and response statuses for game mode and low video memory.
  • Theme resource binding from code. The experimental FrameworkElement.SetThemeResourceBinding API lets apps create the equivalent of a {ThemeResource} binding programmatically.
  • Delegate-based DataTemplate construction. A new experimental DataTemplate constructor accepts an app-provided delegate that creates the template's element subtree.
  • TableView control. The experimental TableView control is now available in the public WinMDs, with grouping, templated group headers, sorting and filtering, resizable columns, and optional cell and header tooltips.
  • Chart control. A new experimental WinUI 3 Chart control presents Cartesian data as line, area, and bar series, with configurable axes, legends, labels, and markers.
  • WinUI 3 inking updates. New InkPresenter.ActivateCustomDrying and InkSynchronizer APIs let apps render committed ink themselves, and InkToolbar now targets an InkPresenter directly.

Bugs fixed:

  • Fixed an access violation that could occur when reading InkPresenter.StrokeContainer while custom drying was active.
  • Fixed InkCanvas presenter sizing under a RenderTransform.
  • Fixed a WinUI resource-tracking issue that could cause memory usage to grow when apps repeatedly created visual-state storyboards or resolved static or theme resources.
  • Improved cleanup of unreachable native WinUI objects in .NET apps after tab or page teardown.

To see everything that's new and changed, see the full Windows App SDK 2.5 Experimental release notes.

Try it out

Getting started

To get started using Windows App SDK to develop Windows apps, check out the following documentation:

Commits viewable in compare view.

Updated Microsoft.WindowsAppSDK from 2.6.4 to 2.6.5.

Release notes

Sourced from Microsoft.WindowsAppSDK's releases.

2.6.5

Windows App SDK 2.6.5 delivers targeted fixes for rendering, window composition, system backdrops, and packaged app installation.

Bug fixes

Bug fix Runtime Compatibility Change
Fixed rendering corruption that could occur on systems with multiple graphics adapters or monitors. N/A, rendering-region fix
Fixed an E_NOINTERFACE crash when enabling the System Composition Engine on Windows builds that lack the required interfaces. The runtime now uses the lifted compositor on those builds. N/A, operating system capability detection fix
Fixed an issue where window backgrounds and GDI controls could become unexpectedly transparent on Windows 10, including apps hosting XAML islands. N/A, window composition ABI fix
Reverted the system backdrop change introduced in 2.6.4 to address wrong-thread exceptions. System backdrops for content islands and XAML windows are not supported when using the System Composition Engine in this release. N/A, revert of a previously contained change
Fixed an issue where app-extension registration metadata generation returned E_NOTIMPL, which could prevent packaged apps from installing. N/A, missing implementation fix

For details, see the full Windows App SDK 2.6.5 release notes.

Try it out

Getting started

To get started using Windows App SDK to develop Windows apps, check out the following documentation:

Commits viewable in compare view.

Pinned NAudio.Core at 2.4.0.

Release notes

Sourced from NAudio.Core's releases.

2.4.0

  • Added DeviceCount and GetCapabilities static methods to WaveOutEvent so output
    devices can be enumerated without referencing NAudio.WinForms (#​1331, #​777)
  • Fixed WASAPI and Media Foundation interop under Unity's Mono runtime, which marshalled
    formatted class parameters as COM interfaces; they are now explicitly marked
    [MarshalAs(UnmanagedType.LPStruct)] (#​1414)

2.3.0

  • Performance improvements for PropertyStore and Core Audio property access (#​1206)
  • Improved multi-channel playback compatibility in WASAPI exclusive mode (#​1234)
  • Fixed a bug that prevented WasapiCapture from using exclusive mode (#​1122)
  • Fixed RF64 header parsing in WaveFileChunkReader.ReadWaveHeader (#​1231)
  • PropVariant now supports VT_EMPTY by returning null (#​1071)
  • Better exception when calling disposed AcmStream.Convert (#​1108)
  • Fixed AcmStreamHeader finalizer crash with corrupted data (#​1199)
  • Added net6.0 targets for NAudio.Asio and NAudio.WinMM to remove registry dependency (#​1139)
  • Updating TFMs, modernizing the UAP project to WinUI

Commits viewable in compare view.

Pinned NAudio.Wasapi at 2.4.0.

Release notes

Sourced from NAudio.Wasapi's releases.

2.4.0

  • Added DeviceCount and GetCapabilities static methods to WaveOutEvent so output
    devices can be enumerated without referencing NAudio.WinForms (#​1331, #​777)
  • Fixed WASAPI and Media Foundation interop under Unity's Mono runtime, which marshalled
    formatted class parameters as COM interfaces; they are now explicitly marked
    [MarshalAs(UnmanagedType.LPStruct)] (#​1414)

2.3.0

  • Performance improvements for PropertyStore and Core Audio property access (#​1206)
  • Improved multi-channel playback compatibility in WASAPI exclusive mode (#​1234)
  • Fixed a bug that prevented WasapiCapture from using exclusive mode (#​1122)
  • Fixed RF64 header parsing in WaveFileChunkReader.ReadWaveHeader (#​1231)
  • PropVariant now supports VT_EMPTY by returning null (#​1071)
  • Better exception when calling disposed AcmStream.Convert (#​1108)
  • Fixed AcmStreamHeader finalizer crash with corrupted data (#​1199)
  • Added net6.0 targets for NAudio.Asio and NAudio.WinMM to remove registry dependency (#​1139)
  • Updating TFMs, modernizing the UAP project to WinUI

Commits viewable in compare view.

Updated QRCoder from 1.6.0 to 1.8.1.

Release notes

Sourced from QRCoder's releases.

1.8.1

What's Changed

New Contributors

Full Changelog: Shane32/QRCoder@v1.8.0...v1.8.1

1.8.0

What's Changed

New Contributors

Full Changelog: Shane32/QRCoder@v1.7.0...v1.8.0

1.7.0

New Features

Performance Enhancements

Bug Fixes

Documentation Changes

Refactoring and Other Changes

Commits viewable in compare view.

@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Nov 13, 2026
Bumps AlphaSkia.Native.Windows from 3.4.135 to 3.5.147
Bumps AlphaTab from 1.8.4 to 1.9.0
Bumps Microsoft.NET.Test.Sdk from 18.11.0 to 18.12.0
Bumps Microsoft.Windows.SDK.BuildTools from 10.0.28000.2705 to 10.0.28000.2957
Bumps Microsoft.WindowsAppSDK to 2.6.5
Bumps NAudio.Core from 2.2.1 to 2.4.0
Bumps NAudio.Wasapi from 2.2.1 to 2.4.0
Bumps QRCoder from 1.6.0 to 1.8.1

---
updated-dependencies:
- dependency-name: AlphaSkia.Native.Windows
  dependency-version: 3.5.147
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: AlphaTab
  dependency-version: 1.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Microsoft.Windows.SDK.BuildTools
  dependency-version: 10.0.28000.2957
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: Microsoft.WindowsAppSDK
  dependency-version: 2.6.5
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: Microsoft.WindowsAppSDK
  dependency-version: 2.6.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: NAudio.Core
  dependency-version: 2.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: NAudio.Wasapi
  dependency-version: 2.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: QRCoder
  dependency-version: 1.8.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title build: Bump the minor-and-patch group with 8 updates build: Bump AlphaSkia.Native.Windows and 7 others Nov 14, 2026
@dependabot
dependabot Bot force-pushed the dependabot/nuget/apps/bandroom/windows/minor-and-patch-2b8f0afb85 branch from 465bf83 to 10729ab Compare November 14, 2026 00:07
181192 added a commit that referenced this pull request Nov 15, 2026
…#537)

## What and why

Moves Studio, Windows (Play, Fretscribe, Bandroom) and the Apple tab
page to alphaTab 1.9.0, with alphaSkia on 3.5.147 everywhere (alphaTab
1.9.0 depends on it; nothing published supports alphaSkia 4.0).
**Android stays on alphaTab 1.8.4**, see below. Also takes the other
bumps of the three Dependabot pull requests.

Supersedes #438, #439 and #442. The alphaSkia 4.0 pull requests #440,
#444, #445 and #446 should be closed; a Dependabot rule now ignores
alphaSkia majors for Gradle and NuGet.

- Studio: `@coderline/alphatab` 1.9.0, playwright, vitest; the committed
bundle is rebuilt.
- Windows: AlphaTab 1.9.0, managed `AlphaSkia` and
`AlphaSkia.Native.Windows` both 3.5.147 (resolved versions checked in
`project.assets.json`), QRCoder 1.8.1, NAudio 2.4.0, WindowsAppSDK
2.6.5, test SDK. Play for Windows numbers every bar.
- Apple: tab page pinned to 1.9.0 (`fetch-alphatab.sh`, checksum updated
and matching the npm tarball).
- Android: AGP 9.5.1, Roborazzi 1.78.0, Gradle 9.9.1 only.

### What alphaTab 1.9.0 changes on screen, and what is kept
- Bar numbers now appear only on the first bar of each system. Every
client sets every bar numbered again (Studio, Windows, Apple tab).
- Wider note spacing (new spacing model): fewer bars per line on a phone
in the same width. Not changed; it is the new default.
- The "rendered by alphaTab" line under the score is gone. A small "♪
alphaTab.net" is drawn above the first system of scores with more than
10 bars or 2 tracks; it cannot be turned off. Studio's 7-bar tab shows
none.
- Deprecated `justifyLastSystem` and `enableUserInteraction` replaced by
their 1.9 settings in the Apple tab page.

### Android stays on 1.8.4
With 1.9.0, Fretscribe's tab never finishes engraving (every Fretscribe
screen with a tab timed out). The Android view sizes its render surface
from the `totalHeight` of the last partial render result, and in 1.9.0 a
partial result carries the top of its own system there. Measured on a
16-bar bass line: surface 4029 px, music ends at 4484 px, so the last
system is not inside the page. The finished render reports the right
total (1751 against 1535 layout units). Correcting it means writing
alphaTab's private `_totalHeight`, which I did not ship. Brasscribe's
score view uses the same surface and Page layout, so it is likely
affected too. Not confirmed on an emulator or phone: I did not run one.

The upstream report is drafted for the owner to file, with the
measurements and a repro, in
`~/private/.brasscribe-review/alphatab-android-issue.md` (with the
16-bar score, an invented bass line from the fixtures, and a Chromium
check that the browser build is not affected).
`TabViewTest.theEngravedPageIsAsTallAsItsMusic` waits for alphaTab's own
`postRenderFinished`, then checks the surface height against the end of
the music: on 1.9.0 it fails on that check ("the page (4029 px) reaches
the end of the music (4484 px)"), on 1.8.4 it passes. It is the gate for
moving Android; the README's Known limits and a Dependabot ignore
(`net.alphatab:alphaTab` >= 1.9.0) say so.


### Pinned, and licence-checked
- Studio pins `@coderline/alphatab` exactly (`1.9.0`, no caret).
Dependabot ignores alphaTab `>=1.10.0` (npm, Gradle, NuGet) and, for
Gradle, `>=1.9.0` until Android's page height is fixed upstream.
- `scripts/licences.py check` now reads the alphaTab version from
Studio's `package.json`, Android's version catalogue, Windows'
`Directory.Packages.props` and `fetch-alphatab.sh`, and fails when one
is not in `checked.versions` of `licences/components.json` (1.8.4 and
1.9.0, whose licence files were compared). A newer pin asks for its
licence to be read first. Tried: a `VERSION=1.10.0` pin and a `^1.9.0`
range both fail it.

### The "alphaTab.net" mark (1.9.0 draws it and asks that it stays
visible)
Recorded in the alphaTab note of `licences/components.json` (so in every
app's licence text); the code now keeps every overlay off it. alphaTab
does not report where the mark is: it is right-aligned to the last bar
of the first system and rests above whatever alphaTab placed over the
top staff, so each client keeps clear of the band above that staff at
the end of the first system (78 layout units wide, scaled), and its own
checks read the mark's real box from the engraving.
- **Windows** (found in this PR's CI screenshot: the repeat highlight's
border covered "alphaTab.ne"): the overlay planner takes the area and
cuts every tint, outline, bracket, line and cursor around it, and lifts
a "?" or a label that would stand on it to just above it
(`ScoreOverlay.KeepClear`, `ScoreGeometry.AttributionArea`). Unit tests:
nothing planned overlaps the area (a loop over the whole first line, a
cursor, groups, marks, ad lib in it), clear overlays are unchanged, and
the area matches the first system of Old Hundredth at two scales. Not
seen on a Windows screen after the change: the CI screenshot will show
it.
- **Studio**: the "?" marks are lifted the same way
(`src/lib/attribution.ts`, vitest). The screen catalogue has a new check
on every view (`attribution`): each "?" and alphaTab's cursor and
selection against the mark's box, and a test that puts a "?" on the mark
and expects the finding.
- **Apple tab page**: a real overlap found: the app's "?" and "!" boxes
reached into the mark. alphaTab rests the mark above the blank text that
keeps the band for a mark, and how tall alphaTab takes that text to be
depends on the font. The page now measures where the mark was really
drawn (the curved outlines of the path that holds it, read after the
render) and, while a box of the app's stands under it, makes the text
taller (from 1.6 line spaces, by 0.4, up to 4.4) and engraves again; the
cursor and the beat wash are cut out of the measured box.
`studio/browser/apple-tab-page.spec.ts` runs the page in Chromium
(alphaTab from the engine bundle, a long bass line with marks at the end
of the first system, scales 1 and 1.5, and a start of 1.0 line spaces
that makes the page adapt) and fails when a box, the cursor or the wash
meets the mark; without the growing step, or without the cursor cut, it
fails. The app's SwiftUI overlay uses the boxes the page reports; not
run on a Mac screen.
- **Fretscribe tabs on Windows** draw no marks over the page, and
Android stays on 1.8.4 (no mark); the Android README says what moving to
1.9 needs.
- Pictures: Studio shows the mark at the top right of the first system,
uncovered; on the Apple page at scale 1 the mark was at 78 to 89 px and
the "?" boxes at 83 to 101 px (overlap) before the change, and above the
boxes after it. Windows and Studio keep out of the whole band above the
first system's top staff at its end, which does not depend on the font.

### What a player sees differently, phone (alphaTab 1.8.4) against
computer (1.9.0)
Fixed in 1.9.0, so still wrong on the phone:
- Accidentals on tied notes and in repeated bars: 1.9.0 spells a note
from the file's step and alter; 1.8.4 spells it from the pitch, so a tie
or a repeat can show another spelling of the same note.
- Repeats, D.C. and D.S. in imported MusicXML: 1.9.0 plays jumps once
and the final pass of a repeat after a jump, and reads jumps written in
a `<sound>` inside a `<direction>`; 1.8.4 can play them in another
order.
- Tempo marked with a dotted quarter: 1.9.0 converts the beat unit to
the quarter-note tempo; 1.8.4 plays it at the wrong speed.
- Also: MusicXML dead notes, string numbers on notation staves and
fingering digits import; spans (slurs, ties) are paired per part and
staff; beaming, count-in and the metronome follow a pick-up bar.
Only on the computer: the new note spacing (wider, so fewer bars per
system at the same width) and the alphaTab.net mark. Bar numbers are on
every bar on both.

### Licences
Checked: alphaTab 1.9.0 LICENSE, Bravura font and licence files and the
Sonivox SoundFont are byte-identical to 1.8.4; npm metadata says MPL-2.0
for 1.9.0 and for the 1.10 alpha. alphaSkia 3.5.147 and the Windows
native package are BSD-3-Clause; QRCoder and NAudio MIT.
`scripts/licences.py check` passes. alphaTab's 1.9 release notes say a
future release will move from MPL-2.0 to a licence with an attribution
clause (CPAL-1.0 is "the best fit so far"); releases up to and including
1.9.0 stay MPL-2.0. 1.9.0 is the newest release confirmed MPL-2.0; do
not move past it without re-reading the licence. Dependabot will propose
later releases.

### Open PR #467 (tab sound on Android)
Its synthesizer classes (`TinySoundFont`, `Hydra`, `Set`, `IReadable`,
`ByteBuffer`) and the methods it calls have identical public signatures
in 1.9.0; only the compiler-mangled internal names on `Float32Array` and
`Uint8Array` (`$android_release` to `$android`) differ, and #467 does
not use those. Android is on 1.8.4 here anyway. The Apple branch
`feat/fretscribe-apple-tab-sound` was not read.

## Areas touched
studio, windows, core-dotnet, apple (tab page), android (versions, one
test, README)

## Verification
- `scripts/check.sh full studio` (with the new catalogue check and the
Apple page spec): pass. `full android`: pass (after one load-related
timeout in `ReadyNotificationTest` that passed alone and on rerun).
`full windows core-dotnet`: pass. `fast apple`: pass.
`scripts/licences.py check`: pass.
- Screenshots compared against main: Studio tab view (bar numbers back,
slightly wider spacing, credit line gone). Android 1.9.0 screenshots
were taken before the fallback (Play score: two bars per line instead of
three, bar numbers only at line starts) and are not repeated for 1.8.4,
which is unchanged.
- Not run: emulator or phone, Windows UI on a real Windows machine,
Apple tab page in a simulator beyond the package tests.

- [x] `make check` for the areas above
- [ ] Tier 3
- [x] Docs updated

## AI assistance
- [x] Mostly: an agent wrote most of it; verification as listed above

## Checklist
- [x] No personal data, machine paths, secrets or copyrighted music
- [x] Goldens untouched

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01AgjPibz4irVFPi2U9TZy4S

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
@181192

181192 commented Nov 15, 2026

Copy link
Copy Markdown
Owner

Superseded by #537 (alphaTab 1.9.0 for Studio, Windows and the Apple tab; alphaSkia stays on 3.5.147).

@181192 181192 closed this Nov 15, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 15, 2026

Copy link
Copy Markdown
Contributor Author

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot
dependabot Bot deleted the dependabot/nuget/apps/bandroom/windows/minor-and-patch-2b8f0afb85 branch November 15, 2026 18:32
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.

1 participant