Skip to content

fix(build): ensure format file triggers publish and loads from source - #94

Merged
jakehildreth merged 1 commit into
mainfrom
fix/include-format-file-in-publish
Aug 3, 2026
Merged

fix(build): ensure format file triggers publish and loads from source#94
jakehildreth merged 1 commit into
mainfrom
fix/include-format-file-in-publish

Conversation

@jakehildreth

Copy link
Copy Markdown
Owner

Summary

Hardens the build/publish pipeline so that LS2Issue.format.ps1xml changes are always included in published packages and the module loads format data correctly when imported from source.

Problem

  • The publish workflow did not trigger on changes to LS2Issue.format.ps1xml, so format-only updates could be skipped during release.
  • The source Locksmith2.psd1 did not declare FormatsToProcess, relying on a runtime fallback in Locksmith2.psm1 for source imports.

Changes

  • Added LS2Issue.format.ps1xml to the push trigger paths in .github/workflows/publish.yml.
  • Added FormatsToProcess = @('LS2Issue.format.ps1xml') to Locksmith2.psd1.

Verification

  • Import-Module Locksmith2.psd1 from source now loads all 21 format views (Default, Summary, 19 *Detailed views, and Full).

Files changed

  • .github/workflows/publish.yml
  • Locksmith2.psd1

- add LS2Issue.format.ps1xml to publish.yml push trigger paths
- add explicit FormatsToProcess to Locksmith2.psd1 for source imports
@jakehildreth
jakehildreth merged commit 8c5402b into main Aug 3, 2026
1 check passed
@jakehildreth
jakehildreth deleted the fix/include-format-file-in-publish branch August 3, 2026 01:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant