Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 1, 2025

This PR contains the following updates:

Package Change Age Confidence Type Update
DotMake.CommandLine (source) 2.4.0 -> 2.7.1 age confidence nuget minor
FluentAssertions (source) 8.3.0 -> 8.6.0 age confidence nuget minor
Hl7.Fhir.R4 5.11.7 -> 5.12.2 age confidence nuget minor
Microsoft.Extensions.DependencyInjection (source) 9.0.5 -> 9.0.8 age confidence nuget patch
Microsoft.Extensions.Logging.Console (source) 9.0.5 -> 9.0.8 age confidence nuget patch
Minio 6.0.4 -> 6.0.5 age confidence nuget patch
Polly.Core 8.5.2 -> 8.6.3 age confidence nuget minor
System.Linq.Async 6.0.1 -> 6.0.3 age confidence nuget patch
Testcontainers (source) 4.4.0 -> 4.7.0 age confidence nuget minor
csharpier 1.0.2 -> 1.1.2 age confidence nuget minor
docker.io/bitnami/minio (source) 2025.5.24-debian-12-r4 -> 2025.7.23-debian-12-r5 age confidence minor
docker.io/bitnami/minio-client (source) 2025.5.21-debian-12-r1 -> 2025.7.21-debian-12-r3 age confidence minor
docker.io/curlimages/curl 8.13.0 -> 8.15.0 age confidence minor
mcr.microsoft.com/dotnet/runtime 9.0.5-noble-chiseled -> 9.0.8-noble-chiseled age confidence final patch
mcr.microsoft.com/dotnet/sdk 9.0.300-noble -> 9.0.304-noble age confidence stage patch
xunit.runner.visualstudio 3.1.0 -> 3.1.4 age confidence nuget patch

Release Notes

dotmake-build/command-line (DotMake.CommandLine)

v2.7.1: DotMake.CommandLine v2.7.1

  • Fixed: Foreground color is always white on macOS regardless of theme settings.

v2.7.0: DotMake.CommandLine v2.7.0

  • Updated to version 2.0.0-beta7.25380.108 of System.CommandLine.

v2.6.8: DotMake.CommandLine v2.6.8

  • Added: Command and RootCommand properties to CliParser class:

    var parser = Cli.GetParser<RootCliCommand>();
    
    //Access the command that is used to parse the command line input.
    var command = parser.Command;
    
    //Access the root of the command that is used to parse the command line input.
    //If parser.Command is already a root command, this will be same instance.
    //If it's a sub-command, it will be the root of that sub-command.
    var rootCommand = parser.RootCommand;
  • Fixed: SourceGenerator sometimes triggers a concurrency exception. Use ConcurrentDictionary for GenerationCounts.

  • Fixed: Do not add auto name or alias for root commands as it can unnecessarily conflict with children.

v2.6.7: DotMake.CommandLine v2.6.7

  • Fixed: Naming related settings were not being inherited correctly after level-2 sub-commands or above.

  • Fixed: NullReferenceException when invoking help output for a sub-command that had completions.

v2.6.6: DotMake.CommandLine v2.6.6

  • Updated to version 2.0.0-beta6.25358.103 of System.CommandLine.
    Also use exact version match with [] for PackageReference as future beta versions can break API.

  • Added: Order property to [CliCommand], [CliDirective], [CliOption] and [CliArgument] attributes.
    The order is used when printing the symbols in help and for arguments additionally effects the parsing order.
    When not set (or is 0 - the default value), the symbol order is determined based on source code ordering.

    [CliCommand(Description = "A root cli command with custom order")]
    public class OrderedCliCommand
    {
        [CliOption(Description = "Description for Option1", Order = 2)]
        public string Option1 { get; set; } = "DefaultForOption1";
    
        [CliOption(Description = "Description for Option2", Order = 1)]
        public string Option2 { get; set; } = "DefaultForOption2";
    
        [CliArgument(Description = "Description for Argument1", Order = 2)]
        public string Argument1 { get; set; } = "DefaultForArgument1";
    
        [CliArgument(Description = "Description for Argument2", Order = 1)]
        public string Argument2 { get; set; } = "DefaultForArgument2";
    
        [CliCommand(Description = "Description for sub-command1", Order = 2)]
        public class Sub1CliCommand
        {
    
        }
    
        [CliCommand(Description = "Description for sub-command2", Order = 1)]
        public class Sub2CliCommand
        {
    
        }
    }
  • Improved: Nested classes with container class not having [CliCommand] attribute, can now be used.

  • Fixed: If there is no HelpName for option and if option is not a flag, show the <argument> next to it, for example:

    Options:
      --settingsfile <settingsfile>  Path to settings file [required]

v2.6.4: DotMake.CommandLine v2.6.4

  • Improved: Even more robust command binding. Added Create, BindCalled, BindAll, IsCalled, Contains methods to CliResult.
    These methods are also available in CliContext.Result which can be accessed in Run command handler.

    var result = Cli.Parse<RootCliCommand>(args);
    
    //Bind now returns null if the command line input does not contain
    //the indicated definition class (as self or as a parent)
    var subCommand = result.Bind<SubCliCommand>();
    //unless you set new returnEmpty parameter to true
    var subCommand2 = result.Bind<SubCliCommand>(true);
    
    //You can get an object for called command
    //without specifying the definition class
    var command = result.BindCalled();
    if (command is SubCliCommand subCommand3)
    {
    
    }
    //Or get an array of objects for all contained commands
    //(self and parents) without specifying the definition class
    var commands = result.BindAll();
    if (commands[0] is SubCliCommand subCommand4)
    {
    
    }
    
    //You can check if the command line input is
    //for the indicated definition class
    if (result.IsCalled<SubCliCommand>())
    {
    
    }
    //You can check if the command line input contains
    //the indicated definition class (as self or as a parent)
    if (result.Contains<SubCliCommand>())
    {
    
    }
    
    //You can create a new instance of the command definition class
    //but without any binding. This is useful for example when you need to
    //instantiate a definition class when using dependency injection.
    var subCommand5 = result.Create<SubCliCommand>();
  • Improved: Command accessor properties can now be safely used for child commands and not only parent commands.
    Circular dependency errors will be prevented, for example when parent and child has command accessors that point to each other.

    [CliCommand(Description = "A root cli command")]
    public class RootCliCommand
    {
        //This will be non-null only when the called command was this sub-command
        //For example you can check sub-command accessors for null to determine
        //which one was called
        public SubCliCommand SubCliCommandAccessor { get; set; }
    
        [CliCommand(Description = "A sub-command")]
        public class SubCliCommand
        {
            //This will be always non-null because if sub-command was called,
            //it's parent-command should also have been called
            public RootCliCommand RootCliCommandAccessor { get; set; }
        }
    }

v2.6.2: DotMake.CommandLine v2.6.2

  • Changed: Renamed Cli.GetConfiguration() to Cli.GetParser() and changed return type from CommandLineConfiguration
    to new class CliParser.
    This method returns a CLI parser configured for the indicated command and you can call Parse or Run methods on it.
    So you can reuse the same CliParser for parsing and running.

    var parser = Cli.GetParser<RootCliCommand>();
    
    var result = parser.Parse(args);
    
    parser.Run(args);

    Changed return type of Cli.Parse methods from ParseResult to new class CliResult which
    describes the results of parsing a command line input based on a specific parser configuration
    and provides methods for binding the result to definition classes.

    var result = Cli.Parse<RootCliCommand>(args);
    
    var rootCliCommand = result.Bind<RootCliCommand>();
    
    if (result.ParseResult.Errors.Count > 0)
    {
    }
  • Improved: More robust command binding. Introduced CliBindingContext for internally encapsulating binders per command build and configuration.
    For example, in previous versions, the below code worked incorrectly, i.e. second call to Cli.Parse with same definition type,
    overwrote the binder so the later Bind call did not work correctly.

    var result = Cli.Parse<RootCliCommand>(args);
    var result2 = Cli.Parse<RootCliCommand>(args);
    
    var rootCommand = result.Bind<RootCliCommand>();

v2.6.0: DotMake.CommandLine v2.6.0

  • Fixed: With v2.5.8, auto short form aliases were still being added even when they already existed, causing the unnecessary conflict error.

  • Fixed: When calling Cli.Run<> with sub-commands but not a root command, help output did not include our custom changes.
    This happened because we were not adding our settings like HelpOption with CustomHelpAction, when the command was not a root command.
    For example, help output showed (as System.CommandLine default output):

    --settingsfile (REQUIRED)  Path to settings file

    where it should show:

    --settingsfile  Path to settings file [required]

    So now, even if it's a sub-command, its root command should be found and those settings should be added there.

    Additionaly, the fix introduced first in v2.0.0 System.CommandLine.RootCommand returned by Cli.GetConfiguration should have correct parents.
    turns out it disabled help output if you used Cli.Run<> with level-2 sub-commands or above,
    due to a subtle bug (root folder was not being populated so help option was lost).

v2.5.8: DotMake.CommandLine v2.5.8

  • Improved: CliNamer to support a parent CliNamer. Unique names were only checked within the command builder
    so the current command was not aware of names of sibling commands. This is now fixed.
    And from now on, we will throw an explanatory exception when there is a name or alias conflict like this:

    System.Exception: CommandAlias 'c' for 'createschema' conflicts with parent CommandAlias for 'checkfornewtools'!

    This is because System.CommandLine threw a vague exception when there was a conflict during parsing:

    System.ArgumentException: An item with the same key has already been added. Key: c

    Unique names are checked for DirectiveName (surrounded with []), CommandName, CommandAlias, OptionName, OptionAlias.
    Auto short form aliases will be always derived from symbol name even when a specific name was specified,
    because if user specifies a specific name with all lowercase like checkfornewtools, we cannot split word boundaries.
    Help output will show short aliases first consistently especially for commands (order by prefix and then by length).

  • Improved: Set the values for the parent command accessors before directive, option and argument properties so that
    property get accessors can access them:

    public class DefaultSettingsCliCommand
    {
        [CliOption]
        public string SettingsFile 
        {
            get => RootCommand.SettingsFile; //<-- Avoid NullReferenceException with `RootCommand` here
            set => RootCommand.SettingsFile = value;
        }
        public RootCliCommand RootCommand { get; set; }
    }          
  • Fixed: Usage of [CliArgument].AllowedValues caused compiler error CS1061 because Argument<T>.AcceptOnlyFromAmong(...)
    was moved to extension method System.CommandLine.ArgumentValidation.AcceptOnlyFromAmong(...) in latest System.CommandLine.

  • Improved: Added empty publish/ folder to the repository. In src/nuget.config we add a custom package source so that we can consume our own built nuget package locally:

    <add key="DotMake Local" value="..\publish" />

    So as the publish/ folder was not commited to the repository, users could have a problem building the project due to NuGet Package Manager complaining about non-existing publish/ folder.

v2.5.6: DotMake.CommandLine v2.5.6

  • Improved: Switched back to using official NuGet feed from DotNet Daily Builds feed for System.CommandLine as now 2.0.0-beta5.25306.1 is released.
    Now the DLL will no more be packed into our package and System.CommandLine will appear as NuGet dependency.

  • Fixed: Error DMCLI01: DotMake.CommandLine.SourceGeneration -> System.ArgumentException: Syntax node is not within syntax tree
    when using partial class for a command which has a nested class for a subcommand.
    Reason: SemanticModel from parent symbol can be different for a child symbol, especially for nested classes in a partial class.
    Solution: Check if SyntaxTree is same for current SemanticModel and SyntaxNode, if not, get a new SemanticModel
    via semanticModel.Compilation.GetSemanticModel(syntaxNode.SyntaxTree).

  • Fixed: The new enum CliNameAutoGenerate in v2.5.0 is a [Flags] enum and it was not translated to C# code correctly
    when multiple flags were combined:

    [CliCommand(
        ShortFormAutoGenerate = CliNameAutoGenerate.Options | CliNameAutoGenerate.Arguments
    )]
    public class RootHelpOnEmptyCliCommand
  • Improved: Added .cmd batch scripts to repository root for easier building:

    1. Build TestApp.cmd
    2. Build Nuget Package.cmd
    3.1. Build TestApp.Nuget.cmd
    3.2. Build TestApp.NugetDI.cmd
    3.3. Build TestApp.NugetAot.cmd
    4. Build Api Docs WebSite.cmd         

    Output results can be found in publish folder.

v2.5.0: DotMake.CommandLine v2.5.0

  • Added: [CliDirective] attribute for properties to define custom directives:

    [CliCommand(Description = "A root cli command with directives")]
    public class DirectiveCliCommand
    {
        [CliDirective]
        public bool Debug { get; set; }
    
        [CliDirective]
        public string Directive2 { get; set; }
    
        [CliDirective]
        public string[] Vars { get; set; }
    
        public void Run(CliContext context)
        {
            if (context.IsEmpty())
                context.ShowHelp();
            else
            {
                Console.WriteLine($"Directive '{nameof(Debug)}' = {StringExtensions.FormatValue(Debug)}");
                Console.WriteLine($"Directive '{nameof(Directive2)}' = {StringExtensions.FormatValue(Directive2)}");
                Console.WriteLine($"Directive '{nameof(Vars)}' = {StringExtensions.FormatValue(Vars)}");
            }
        }
    }

    Currently only bool, string and string[] types are supported for [CliDirective] properties.
    Here is sample usage and output:

    src\TestApp\bin\Debug\net8.0>TestApp [debug] [directive-2:val1] [vars:val2] [vars:val3]
    Directive 'Debug' = true
    Directive 'Directive2' = "val1"
    Directive 'Vars' = ["val2", "val3"]
  • Improved: CliNameCasingConvention will now generate better CLI identifiers, i.e. it will treat unicode letter casing
    and unicode numbers in class and property names correctly. StringExtensions.ToCase() will handle strings that contain
    unicode space and punctuation characters correctly.

  • Improved: Smarter auto-generated short form aliases. In previous versions, only first letter was added as short form
    if it wasn't already used. Now letters of every word in the option name will be used to reduce conflicts.
    Also short form aliases will now also be generated for commands.

    public class ShortFormCliCommand
    {
            [CliOption(Alias = "o2")]
            public string Oauth2GrantType { get; set; } = "";
    
            [CliOption]
            public string Oauth2TokenUrl { get; set; } = "";
    
            [CliOption]
            public string Oauth2ClientId { get; set; } = "";
    
            [CliOption]
            public string Oauth2ClientSecret { get; set; } = "";
    
            [CliOption]
            public string Sha256 { get; set; } = "";
    }
    Options:
      -o2, --oauth-2-grant-type
      -o2tu, --oauth-2-token-url
      -o2ci, --oauth-2-client-id
      -o2cs, --oauth-2-client-secret
      -s256, --sha-256
  • Added: Alias property to CliCommand and CliOption attributes in addition to existing Aliases property.
    Alias property is more useful, as most of the time you will want to add a single alias which is usually a short form alias.
    When this property is set, it will override the auto-generated short form alias so when you are not happy with a specific
    auto-generated alias you can override it instead of disabling all via ShortFormAutoGenerate = false.

    When manually setting this property, if you don't specify a prefix, it will be prefixed automatically according
    to ShortFormPrefixConvention (e.g. -o or --o or /o) unless it's set to newly added CliNamePrefixConvention.None.
    This will now be also same for existing Aliases property but except, aliases without prefix will be prefixed automatically
    according to NamePrefixConvention instead.

  • Added: CliNameAutoGenerate enum and changed type of [CliCommand].ShortFormAutoGenerate from bool to this enum.
    Added new[CliCommand].NameAutoGenerate property with same enum.
    Auto-generated names can be disabled for all or specific CLI symbol types via [CliCommand].NameAutoGenerate.
    Auto-generated short form aliases can be disabled for all or specific CLI symbol types via [CliCommand].ShortFormAutoGenerate.

v2.4.3: DotMake.CommandLine v2.4.3

  • Fixed: In previous version, using System.Runtime.CompilerServices.RuntimeHelpers.GetUninitializedObject caused IL2072 trimming warnings.
    We now changed handling of completions so that we never need an uninitialized instance of definition type, thus removed usage of GetUninitializedObject to fix the issue:

    • ICliAddCompletions interface is now renamed to ICliGetCompletions.
    • void AddCompletions(string propertyName, List<Func<CompletionContext, IEnumerable<CompletionItem>>> completionSources) interface method
      is now changed to IEnumerable<CompletionItem> GetCompletions(string propertyName, CompletionContext completionContext).

    So now, instead we will use Bind method to get cached definition instance and call GetCompletions interface method.
    The signature change also made implementing interface method more easy and straightforward.

v2.4.2: DotMake.CommandLine v2.4.2

  • Updated to daily build 2.0.0-beta5.25302.104 of System.CommandLine (cannot update beyond this version for now, as Help related classes are made internal).

  • Improved: In previous versions, for setting DefaultValueFactory of options and arguments, a default instance of definition type was being created and its properties were being accessed.
    However if you used dependency injection, this caused unnecessary instantiations because every definition type in the hierarchy had to be instantiated for building the command hierarchy.
    From now on, CliCommandBuilder.Build method will not create a default instance of definition type to avoid IServiceProvider instantiations for other commands in the hierarchy.
    Instead, we will read the property initializer's SyntaxNode, fully-qualify symbols and then use that SyntaxNode directly for setting DefaultValueFactory.
    However, we still need an uninitialized instance for being able to call AddCompletions method that comes with ICliAddCompletions interface, for now.
    The uninitialized instance can not be used for property access, as the constructor is skipped, properties will come as null but it can be used for calling method access.
    Creating an uninitialized instance will not trigger dependency injection, so the problem will be avoided.

  • Fixed: Property initializers were being checked for SyntaxKind.NullKeyword where they should be checked for SyntaxKind.NullLiteralExpression instead
    to auto-determine Required = true when it's not specified explicitly.

fluentassertions/fluentassertions (FluentAssertions)

v8.6.0

Compare Source

What's Changed
Improvements
Others
New Contributors

Full Changelog: fluentassertions/fluentassertions@8.5.0...8.6.0

v8.5.0

Compare Source

What's Changed
New features
Fixes
Others

Full Changelog: fluentassertions/fluentassertions@8.4.0...8.5.0

v8.4.0

Compare Source

What's Changed
Improvements
Others
New Contributors

Full Changelog: fluentassertions/fluentassertions@8.3.0...8.4.0

FirelyTeam/firely-net-sdk (Hl7.Fhir.R4)

v5.12.2: 5.12.2

Intro:

Added FHIRPath debug tracer.
Fixes bugs related to paralelization when using SerializationFilter.
Optimization tweaks.

Changes:
  • #​3260: The ModelInfo.ModelInspector property was pretty expensive
  • #​3261: Include PVAL109 in recoverable issues
  • #​3210: Introduce a fhirpath debug tracer
  • #​3227: Bump BenchmarkDotNet and Fhir.Metrics
  • #​3229: Fix build issue with Fhir.Metrics 1.3.1 nullability annotations
  • #​3218: Fix thread-safety issue with SerializationFilter when reusing JsonSerializerOptions
  • #​3224: Fix NullReferenceException in primitive types GetHashCode() when Value is null
  • #​3217: Implement canonical version matching for partial versions in FHIR validation
  • #​3171: Patient.Validate(true) throws "Object reference not set to an instance of an object." Exception when Data Absent Extension Used.
  • #​3220: Start development phase 5.12.2

This list of changes was auto generated.

v5.12.1: 5.12.1

What's Changed

Full Changelog: FirelyTeam/firely-net-sdk@v5.12.0...v5.12.1

v5.12.0: 5.12.0

Intro:

Added an FHIR R6-ballot3 sattelite and Nuget package.

Changes:
  • #​3186: Update dependabot.yml
  • #​3184: 3109 Add new R6 Satellite
  • #​3183: Re-run codegen on all FHIR versions.
  • #​3182: Clear out contentRef when copying children into an element.
  • #​3158: Start development phase 5.11.8

This list of changes was auto generated.

dotnet/runtime (Microsoft.Extensions.DependencyInjection)

v9.0.8: .NET 9.0.8

Release

What's Changed

Full Changelog: dotnet/runtime@v9.0.7...v9.0.8

v9.0.7: .NET 9.0.7

Release

What's Changed

Full Changelog: dotnet/runtime@v9.0.6...v9.0.7

v9.0.6

Bug Fixes
  • Read messages from binlog if process output is missing build finished message (#​114676)
    Improves reliability of the WebAssembly build process by reading messages from the binlog when the process output does not contain the expected build finished message, preventing build failures in certain scenarios.

  • Fix debugger app hangs related to thread exit (#​114917)
    Resolves an issue where applications could hang during debugging when threads exit, ensuring smoother debugging experiences and preventing deadlocks.

  • [Mono] Workaround MSVC miscompiling sgen_clz (#​114903)
    Addresses a compiler miscompilation issue in MSVC affecting the Mono garbage collector, improving runtime stability and correctness on affected platforms.

  • Do not set the salt or info if they are NULL for OpenSSL HKDF (#​114877)
    Fixes a cryptographic issue by ensuring that the salt or info parameters are not set when they are NULL in OpenSSL HKDF, preventing potential errors or unexpected behavior in key derivation.

  • [Test Only] Fix Idn tests (#​115032)
    Corrects issues in Internationalized Domain Name (Idn) tests, ensuring accurate and reliable test results for domain name handling.

  • JIT: revised fix for fp division issue in profile synthesis (#​115026)
    Provides a more robust fix for floating-point division issues in JIT profile synthesis, improving numerical accuracy and preventing incorrect calculations.

  • Handle OSSL 3.4 change to SAN:othername formatting (#​115361)
    Updates certificate handling to accommodate changes in Subject Alternative Name (SAN) formatting introduced in OpenSSL 3.4, ensuring compatibility and correct parsing of certificates.

  • [Mono] Fix c11 ARM64 atomics to issue full memory barrier (#​115635)
    Fixes atomic operations on ARM64 in Mono to issue a full memory barrier, ensuring correct synchronization and preventing subtle concurrency bugs.

Performance Improvements
  • [WinHTTP] Certificate caching on WinHttpHandler to eliminate extra call to Custom Certificate Validation (#​114678)
    Improves HTTP performance by caching certificates in WinHttpHandler, reducing redundant calls to custom certificate validation and speeding up secure connections.

  • Improve distribute_free_regions (#​115167)
    Optimizes memory management by enhancing the algorithm for distributing free memory regions, leading to better memory utilization and potentially improved application performance.

Technical Improvements
  • Strip trailing slash from source dir for cmake4 (#​114905)
    Refines build scripts by removing trailing slashes from source directories when using CMake 4, preventing potential build path issues and improving build reliability.

  • Don't expose TrustedCertificatesDirectory() and StartNewTlsSessionContext() to NetFx (#​114995)
    Restricts certain internal APIs from being exposed to .NET Framework, reducing surface area and preventing unintended usage.

  • Add support for more libicu versions (#​115376)
    Expands compatibility by supporting additional versions of the International Components for Unicode (ICU) library, enhancing globalization features across more environments.

Infrastructure
  • Run outerloop pipeline only for release branches, not staging/preview (#​115011)
    Optimizes CI/CD resources by limiting the outerloop pipeline to run only on release branches, reducing unnecessary test runs and speeding up development workflows.

  • **Update CentOS Stream, Debian, OpenSUSE ([#​115


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions
Copy link

github-actions bot commented Jul 1, 2025

🦙 MegaLinter status: ⚠️ WARNING

Descriptor Linter Files Fixed Errors Warnings Elapsed time
⚠️ CSHARP csharpier 11 1 0 1.76s
⚠️ CSHARP roslynator 3 3 0 22.3s
✅ DOCKERFILE hadolint 1 0 0 0.13s
✅ EDITORCONFIG editorconfig-checker 40 0 0 2.09s
✅ JSON jsonlint 9 0 0 0.15s
✅ JSON prettier 9 0 0 0.59s
✅ JSON v8r 9 0 0 5.2s
✅ MARKDOWN markdownlint 2 0 0 0.53s
✅ REPOSITORY checkov yes no no 22.58s
✅ REPOSITORY dustilock yes no no 0.03s
✅ REPOSITORY gitleaks yes no no 27.49s
✅ REPOSITORY git_diff yes no no 0.26s
✅ REPOSITORY grype yes no no 39.88s
✅ REPOSITORY kics yes no no 5.19s
✅ REPOSITORY secretlint yes no no 2.48s
✅ REPOSITORY syft yes no no 2.04s
✅ REPOSITORY trivy yes no no 9.04s
✅ REPOSITORY trivy-sbom yes no no 0.27s
✅ REPOSITORY trufflehog yes no no 6.41s
✅ YAML prettier 5 0 0 0.63s
✅ YAML v8r 5 0 0 6.35s
✅ YAML yamllint 5 0 0 0.47s

See detailed report in MegaLinter reports

You could have same capabilities but better runtime performances if you request a new MegaLinter flavor.

MegaLinter is graciously provided by OX Security

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 31b0cac to 1df3525 Compare July 7, 2025 23:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1df3525 to 8330ec4 Compare July 8, 2025 18:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8330ec4 to 8a83b12 Compare July 8, 2025 23:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 326441f to ed305f5 Compare July 15, 2025 04:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 4f3adfd to 43cd582 Compare July 17, 2025 19:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from b9bb55b to 6e5db55 Compare July 25, 2025 23:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6e5db55 to 1583e77 Compare July 30, 2025 12:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1583e77 to 733a7d5 Compare July 30, 2025 19:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 733a7d5 to f7cb224 Compare August 3, 2025 17:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 1ae2bff to 8f894ee Compare August 5, 2025 21:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8f894ee to 11c09fa Compare August 6, 2025 00:48
src/PathlingS3Import/PathlingS3Import.csproj

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/runtime:9.0.5-noble-chiseled@sha256:bd4288d187eac2d9753e4623e0466b9ceec2b340254a640858d3ebb1b25afbac
FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/runtime:9.0.8-noble-chiseled@sha256:90846e7c7ea66c8464341fd8c5e92a598beaf12bdad68b201fce137536f8ac7e

Check notice

Code scanning / KICS (MegaLinter REPOSITORY_KICS)

Healthcheck Instruction Missing Note

Dockerfile doesn't contain instruction 'HEALTHCHECK'
src/PathlingS3Import/PathlingS3Import.csproj

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/runtime:9.0.5-noble-chiseled@sha256:bd4288d187eac2d9753e4623e0466b9ceec2b340254a640858d3ebb1b25afbac
FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/runtime:9.0.8-noble-chiseled@sha256:90846e7c7ea66c8464341fd8c5e92a598beaf12bdad68b201fce137536f8ac7e

Check notice

Code scanning / KICS (MegaLinter REPOSITORY_KICS)

Using Platform Flag with FROM Command

FROM={--platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/runtime:9.0.8-noble-chiseled@sha256:90846e7c7ea66c8464341fd8c5e92a598beaf12bdad68b201fce137536f8ac7e}.{FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/runtime:9.0.8-noble-chiseled@sha256:90846e7c7ea66c8464341fd8c5e92a598beaf12bdad68b201fce137536f8ac7e} is using the '--platform' flag
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from c7e96b8 to aef4dd9 Compare August 11, 2025 12:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 6308eb3 to 316307a Compare August 19, 2025 21:09
@@ -1,4 +1,4 @@
FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:9.0.300-noble@sha256:9f7bd4d010026e15a57d9cf876f2f7d08c3eeed6a0ea987b8c5ba8c75e68e948 AS build
FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:9.0.304-noble@sha256:0b7186a7247bf8c07085fd700613bb0425a6f8f6467a0342c12a535e767da803 AS build

Check notice

Code scanning / KICS (MegaLinter REPOSITORY_KICS)

Using Platform Flag with FROM Command

FROM={--platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:9.0.304-noble@sha256:0b7186a7247bf8c07085fd700613bb0425a6f8f6467a0342c12a535e767da803 AS build}.{FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:9.0.304-noble@sha256:0b7186a7247bf8c07085fd700613bb0425a6f8f6467a0342c12a535e767da803 AS build} is using the '--platform' flag
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 50d7d6f to 9956a41 Compare August 28, 2025 16:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9956a41 to 1ade8f1 Compare September 2, 2025 20:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant