gix-lock v26.0.0

New Features (BREAKING)

• apply shared permissions to locks and parent directories

  Locks in shared repositories need consistent permissions on both the lock
  file and any parent directories created during acquisition. Adjusting only
  the file can leave those directories inaccessible to other repository users.

  Use one explicit parsed Git sharing policy for writable locks, markers,
  and newly created directories. Apply it after the process umask in the
  common acquisition path and forward it to gix-tempfile for directory
  creation. A policy of 0 keeps the umask behavior without permission
  metadata access. The adjusted file mode reaches the committed resource.

  Keep boundary_directory as Option<PathBuf> and pass the sharing policy
  separately. Replace custom-permission and symlink convenience methods with
  File::acquire() and its optional resource resolver. Tests cover lock,
  marker, and committed-resource modes, directory permissions, and rollback.

Commit Statistics

• 7 commits contributed to the release over the course of 13 calendar days.
• 13 days passed between releases.
• 1 commit was understood as conventional.
• 0 issues like '(#ID)' were seen in commit messages

Commit Details

view details

• Uncategorized
  • Prepare changelogs prior to release (794eeef)
  • Merge pull request #3032 from GitoxideLabs/sec-audit (1d7bac7)
  • Merge pull request #3033 from GitoxideLabs/gix-cli-progress-cleanup (80f4b03)
  • Merge pull request #3022 from GitoxideLabs/release-testtools (f819565)
  • Merge pull request #2977 from GitoxideLabs/worktree-create (d9f7c85)
  • Apply shared permissions to locks and parent directories (01b7a58)
  • Merge pull request #3020 from GitoxideLabs/report-september (5fb3dcf)