Merge pull request #331 from betwixt-labs/jsr-fixes #162
publish.yml
on: push
Annotations
1 error and 97 warnings
publish-packages
Process completed with exit code 1.
|
build-compiler (macos-latest)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: falti/[email protected], actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
build-compiler (macos-latest):
extensions/chord.common/Extensions/StringExtensions.cs#L53
Possible null reference assignment.
|
build-compiler (macos-latest):
extensions/chord.common/Extensions/StringExtensions.cs#L58
Possible null reference assignment.
|
build-compiler (macos-latest):
extensions/chord.common/Extensions/StringExtensions.cs#L59
Possible null reference assignment.
|
build-compiler (macos-latest)
Spectre.Console.TypeNameHelper.ProcessType(StringBuilder,Type,TypeNameHelper.DisplayNameOptions): Using member 'System.Reflection.Module.Name.get' which has 'RequiresAssemblyFilesAttribute' can break functionality when embedded in a single-file app. Returns <Unknown> for modules with no file path.
|
build-compiler (macos-latest)
Spectre.Console.TypeNameHelper.ProcessGenericType(StringBuilder,Type,Type[],Int32,TypeNameHelper.DisplayNameOptions): Using member 'System.Reflection.Module.Name.get' which has 'RequiresAssemblyFilesAttribute' can break functionality when embedded in a single-file app. Returns <Unknown> for modules with no file path.
|
build-compiler (macos-latest)
Spectre.Console.TypeNameHelper.ProcessType(StringBuilder,Type,TypeNameHelper.DisplayNameOptions): Using member 'System.Reflection.Module.Name.get' which has 'RequiresAssemblyFilesAttribute' can break functionality when embedded in a single-file app. Returns <Unknown> for modules with no file path.
|
build-compiler (macos-latest)
Spectre.Console.TypeNameHelper.ProcessGenericType(StringBuilder,Type,Type[],Int32,TypeNameHelper.DisplayNameOptions): Using member 'System.Reflection.Module.Name.get' which has 'RequiresAssemblyFilesAttribute' can break functionality when embedded in a single-file app. Returns <Unknown> for modules with no file path.
|
build-compiler (macos-latest):
extensions/chord.common/Extensions/StringExtensions.cs#L53
Possible null reference assignment.
|
build-compiler (macos-latest):
extensions/chord.common/Extensions/StringExtensions.cs#L58
Possible null reference assignment.
|
build-compiler (macos-latest):
extensions/chord.common/Extensions/StringExtensions.cs#L59
Possible null reference assignment.
|
build-compiler (macos-latest):
Core/Meta/JsonContext.cs#L83
Using member 'System.Text.Json.JsonSerializer.Serialize<TValue>(Utf8JsonWriter, TValue, JsonSerializerOptions)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext, or make sure all of the required types are preserved.
|
build-compiler (ubuntu-22.04)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: falti/[email protected], actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
build-compiler (ubuntu-22.04):
extensions/chord.common/Extensions/StringExtensions.cs#L53
Possible null reference assignment.
|
build-compiler (ubuntu-22.04):
extensions/chord.common/Extensions/StringExtensions.cs#L58
Possible null reference assignment.
|
build-compiler (ubuntu-22.04):
extensions/chord.common/Extensions/StringExtensions.cs#L59
Possible null reference assignment.
|
build-compiler (ubuntu-22.04)
Spectre.Console.TypeNameHelper.ProcessType(StringBuilder,Type,TypeNameHelper.DisplayNameOptions): Using member 'System.Reflection.Module.Name.get' which has 'RequiresAssemblyFilesAttribute' can break functionality when embedded in a single-file app. Returns <Unknown> for modules with no file path.
|
build-compiler (ubuntu-22.04)
Spectre.Console.TypeNameHelper.ProcessGenericType(StringBuilder,Type,Type[],Int32,TypeNameHelper.DisplayNameOptions): Using member 'System.Reflection.Module.Name.get' which has 'RequiresAssemblyFilesAttribute' can break functionality when embedded in a single-file app. Returns <Unknown> for modules with no file path.
|
build-compiler (ubuntu-22.04)
Spectre.Console.TypeNameHelper.ProcessType(StringBuilder,Type,TypeNameHelper.DisplayNameOptions): Using member 'System.Reflection.Module.Name.get' which has 'RequiresAssemblyFilesAttribute' can break functionality when embedded in a single-file app. Returns <Unknown> for modules with no file path.
|
build-compiler (ubuntu-22.04)
Spectre.Console.TypeNameHelper.ProcessGenericType(StringBuilder,Type,Type[],Int32,TypeNameHelper.DisplayNameOptions): Using member 'System.Reflection.Module.Name.get' which has 'RequiresAssemblyFilesAttribute' can break functionality when embedded in a single-file app. Returns <Unknown> for modules with no file path.
|
build-compiler (ubuntu-22.04):
extensions/chord.common/Extensions/StringExtensions.cs#L53
Possible null reference assignment.
|
build-compiler (ubuntu-22.04):
extensions/chord.common/Extensions/StringExtensions.cs#L58
Possible null reference assignment.
|
build-compiler (ubuntu-22.04):
extensions/chord.common/Extensions/StringExtensions.cs#L59
Possible null reference assignment.
|
build-compiler (ubuntu-22.04):
Core/Meta/JsonContext.cs#L83
Using member 'System.Text.Json.JsonSerializer.Serialize<TValue>(Utf8JsonWriter, TValue, JsonSerializerOptions)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext, or make sure all of the required types are preserved.
|
build-compiler (ubuntu-22.04):
extensions/chord.common/Extensions/StringExtensions.cs#L53
Possible null reference assignment.
|
build-compiler (ubuntu-22.04):
extensions/chord.common/Extensions/StringExtensions.cs#L58
Possible null reference assignment.
|
build-compiler (ubuntu-22.04):
extensions/chord.common/Extensions/StringExtensions.cs#L59
Possible null reference assignment.
|
build-compiler (ubuntu-22.04):
Core/Meta/JsonContext.cs#L83
Using member 'System.Text.Json.JsonSerializer.Serialize<TValue>(Utf8JsonWriter, TValue, JsonSerializerOptions)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext, or make sure all of the required types are preserved.
|
build-compiler (ubuntu-22.04):
Compiler/Commands/LanguageServerCommand.cs#L21
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
build-compiler (ubuntu-22.04):
Compiler/Commands/BuildCommand.cs#L54
CopyTo synchronously blocks. Await CopyToAsync instead. (https://github.com/Microsoft/vs-threading/blob/master/doc/analyzers/VSTHRD103.md)
|
build-compiler (windows-latest)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: falti/[email protected], actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
build-compiler (windows-latest):
extensions/chord.common/Extensions/StringExtensions.cs#L53
Possible null reference assignment.
|
build-compiler (windows-latest):
extensions/chord.common/Extensions/StringExtensions.cs#L58
Possible null reference assignment.
|
build-compiler (windows-latest):
extensions/chord.common/Extensions/StringExtensions.cs#L59
Possible null reference assignment.
|
build-compiler (windows-latest)
Spectre.Console.TypeNameHelper.ProcessType(StringBuilder,Type,TypeNameHelper.DisplayNameOptions): Using member 'System.Reflection.Module.Name.get' which has 'RequiresAssemblyFilesAttribute' can break functionality when embedded in a single-file app. Returns <Unknown> for modules with no file path.
|
build-compiler (windows-latest)
Spectre.Console.TypeNameHelper.ProcessGenericType(StringBuilder,Type,Type[],Int32,TypeNameHelper.DisplayNameOptions): Using member 'System.Reflection.Module.Name.get' which has 'RequiresAssemblyFilesAttribute' can break functionality when embedded in a single-file app. Returns <Unknown> for modules with no file path.
|
build-compiler (windows-latest)
Spectre.Console.TypeNameHelper.ProcessType(StringBuilder,Type,TypeNameHelper.DisplayNameOptions): Using member 'System.Reflection.Module.Name.get' which has 'RequiresAssemblyFilesAttribute' can break functionality when embedded in a single-file app. Returns <Unknown> for modules with no file path.
|
build-compiler (windows-latest)
Spectre.Console.TypeNameHelper.ProcessGenericType(StringBuilder,Type,Type[],Int32,TypeNameHelper.DisplayNameOptions): Using member 'System.Reflection.Module.Name.get' which has 'RequiresAssemblyFilesAttribute' can break functionality when embedded in a single-file app. Returns <Unknown> for modules with no file path.
|
build-compiler (windows-latest):
extensions/chord.common/Extensions/StringExtensions.cs#L53
Possible null reference assignment.
|
build-compiler (windows-latest):
extensions/chord.common/Extensions/StringExtensions.cs#L58
Possible null reference assignment.
|
build-compiler (windows-latest):
extensions/chord.common/Extensions/StringExtensions.cs#L59
Possible null reference assignment.
|
build-compiler (windows-latest):
Core/Meta/JsonContext.cs#L83
Using member 'System.Text.Json.JsonSerializer.Serialize<TValue>(Utf8JsonWriter, TValue, JsonSerializerOptions)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext, or make sure all of the required types are preserved.
|
build-runtimes
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v1, falti/[email protected], actions/setup-dotnet@v3, actions/upload-artifact@v3, actions-rs/toolchain@v1, actions/download-artifact@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
build-runtimes
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1, falti/[email protected], actions-rs/toolchain@v1, actions/download-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build-runtimes:
Core/Meta/JsonContext.cs#L83
Using member 'System.Text.Json.JsonSerializer.Serialize<TValue>(Utf8JsonWriter, TValue, JsonSerializerOptions)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext, or make sure all of the required types are preserved.
|
build-runtimes
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-runtimes
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-runtimes
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-runtimes
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-runtimes:
extensions/chord.common/Extensions/StringExtensions.cs#L53
Possible null reference assignment.
|
build-runtimes:
extensions/chord.common/Extensions/StringExtensions.cs#L58
Possible null reference assignment.
|
build-runtimes:
extensions/chord.common/Extensions/StringExtensions.cs#L59
Possible null reference assignment.
|
build-runtimes:
Core/Meta/JsonContext.cs#L83
Using member 'System.Text.Json.JsonSerializer.Serialize<TValue>(Utf8JsonWriter, TValue, JsonSerializerOptions)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext, or make sure all of the required types are preserved.
|
build-runtimes
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-runtimes
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-runtimes
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-runtimes
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-runtimes
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-tools
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions-rs/toolchain@v1, actions/setup-node@v1, falti/[email protected], actions/download-artifact@v2, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
build-tools
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions/setup-node@v1, falti/[email protected], actions/download-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build-tools
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-tools
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-tools
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-tools
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-tools
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-tools
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-tools
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-tools
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
build-tools
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "bebop-runtime-cs-3.0.8", "bebop-runtime-rust-3.0.8", "bebop-runtime-ts-3.0.8", "bebop-tools-cargo-3.0.8", "bebop-tools-npm-3.0.8", "bebop-tools-nuget-3.0.8", "chordc-linux-arm64", "chordc-linux-x64", "chordc-osx-arm64", "chordc-osx-x64", "chordc-win-arm64", "chordc-win-x64", "linux-arm64", "linux-x64", "osx-arm64", "osx-x64", "vscode-bebop", "wasi-wasm", "win-arm64", "win-x64".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
publish-packages
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v1, falti/[email protected], actions/setup-dotnet@v1, actions-rs/toolchain@v1, actions/download-artifact@v2, actions/create-release@v1, actions/upload-release-asset@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
publish-packages
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1, falti/[email protected], actions/setup-dotnet@v1, actions-rs/toolchain@v1, actions/download-artifact@v2, actions/create-release@v1, actions/upload-release-asset@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
publish-packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
bebop-runtime-cs-3.0.8
Expired
|
185 KB |
|
bebop-runtime-rust-3.0.8
Expired
|
16.2 KB |
|
bebop-runtime-ts-3.0.8
Expired
|
88.4 KB |
|
bebop-tools-cargo-3.0.8
Expired
|
6.12 KB |
|
bebop-tools-npm-3.0.8
Expired
|
77.1 MB |
|
bebop-tools-nuget-3.0.8
Expired
|
75.3 MB |
|
chordc-linux-arm64
Expired
|
4.49 MB |
|
chordc-linux-x64
Expired
|
4.64 MB |
|
chordc-osx-arm64
Expired
|
4.56 MB |
|
chordc-osx-x64
Expired
|
4.73 MB |
|
chordc-win-arm64
Expired
|
3.86 MB |
|
chordc-win-x64
Expired
|
3.95 MB |
|
linux-arm64
Expired
|
13.2 MB |
|
linux-x64
Expired
|
13.6 MB |
|
osx-arm64
Expired
|
12.7 MB |
|
osx-x64
Expired
|
13.6 MB |
|
vscode-bebop
Expired
|
78 MB |
|
wasi-wasm
Expired
|
4.92 MB |
|
win-arm64
Expired
|
9.6 MB |
|
win-x64
Expired
|
12.6 MB |
|