Repository navigation
fix(settings): normalize file-only ACL flags #31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,12 +5,12 @@ | |
| <Authors>Kibnet</Authors> | ||
| <RepositoryUrl>https://github.com/Kibnet/WritableJsonConfiguration</RepositoryUrl> | ||
| <PackageProjectUrl>https://github.com/Kibnet/WritableJsonConfiguration</PackageProjectUrl> | ||
| <PackageVersion>8.1.1</PackageVersion> | ||
| <PackageVersion>8.1.2</PackageVersion> | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
When this version is packed and published, Useful? React with 👍 / 👎. |
||
| <Description>Source of configurations in JSON format with the ability to edit values directly from the running application. Based on Microsoft.Extensions.Configuration.</Description> | ||
| <PackageIcon>JSON_logo.png</PackageIcon> | ||
| <PackageReadmeFile>README.md</PackageReadmeFile> | ||
| <PackageLicenseExpression>MIT</PackageLicenseExpression> | ||
| <PackageReleaseNotes>Fix atomic-path handling for numeric object keys and reject sparse array indexes instead of writing a different index.</PackageReleaseNotes> | ||
| <PackageReleaseNotes>Fix false atomic-write ACL mismatches after Windows normalizes equivalent file access entries during File.Replace.</PackageReleaseNotes> | ||
| </PropertyGroup> | ||
|
|
||
| <ItemGroup> | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On pushes to
master, this newly added job runs independently of the existingbuildjob, whose final steps publish the package to NuGet and GitHub. Because jobs without aneedsrelationship run in parallel, version 8.1.2 can be published before these Windows-only tests finish—and remains published even if they fail—so the new coverage does not protect releases of the Windows-only atomic-write path. Move publishing into a job that depends on both test jobs, or otherwise make publishing wait forwindows-tests.Useful? React with 👍 / 👎.