Skip to content

fix: change extension to mjs to resolve error #99

fix: change extension to mjs to resolve error

fix: change extension to mjs to resolve error #99

Triggered via push April 1, 2024 17:17
Status Success
Total duration 2m 4s
Artifacts
Deploy to GitHub Pages
1m 54s
Deploy to GitHub Pages
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
Deploy to GitHub Pages
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-dotnet@v3, actions/setup-node@v3, peaceiris/actions-gh-pages@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Deploy to GitHub Pages
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
Deploy to GitHub Pages: src/KafkaFlow.Abstractions/Configuration/TopicPartitions.cs#L5
Missing XML comment for publicly visible type or member 'TopicPartitions'
Deploy to GitHub Pages: src/KafkaFlow.Abstractions/Configuration/TopicPartitions.cs#L7
Missing XML comment for publicly visible type or member 'TopicPartitions.TopicPartitions(string, IEnumerable<int>)'
Deploy to GitHub Pages: src/KafkaFlow.Abstractions/Configuration/TopicPartitions.cs#L13
Missing XML comment for publicly visible type or member 'TopicPartitions.Name'
Deploy to GitHub Pages: src/KafkaFlow.Abstractions/Configuration/TopicPartitions.cs#L15
Missing XML comment for publicly visible type or member 'TopicPartitions.Partitions'