chore(release): 0.5.0 (#200)

## [0.5.0] - 2026-08-16

### Added

- Version ranges in the `Version` field using NuGet range syntax (e.g.
  `'[2.2.3,3.0)'`, `'[2.0,)'`, `'(,3.0)'`) for the `PSGalleryModule`,
  `PSResourceGet`, and `PSGalleryNuget` dependency types. A bare version
  (e.g. `'3.2.1'`) still means that exact version; a range installs the
  highest available version that satisfies it (#65, #91, #199).
- `FileDownload` is now supported on all platforms (`windows`, `core`,
  `macos`, `linux`); there was no Windows-only code blocking this
  (#98, #193).
- `FileDownload` relative `Target` paths are now rooted against `$PWD`
  before resolution, matching the intuitive expectation of callers
  (#49, #193).

### Fixed

- `Get-Dependency -InputObject` no longer mutates the caller's
hashtable:
`PSDependOptions` is now preserved after the call, so a second
invocation
  with the same object still honors global options such as `Target`
  (#35, #192).
- `FileDownload` no longer misidentifies a directory-like `Target` (no
  file extension, or trailing slash) as a full file path when its parent
  happens to exist; the handler now uses a file-extension heuristic to
distinguish file targets from container targets and creates the
directory
  when it does not yet exist (#49, #193).
- `Git` handler no longer silently ignores a pre-existing directory at
  the clone target that is not a valid git repository; it now emits a
  `Write-Warning` so the user knows why the install was skipped
  (#86, #194).

chore: promote 0.4.1 to stable by clearing prerelease tag

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

ci: delegate to PowerShellOrg reusable workflows (#184)

## Summary

- **CI.yml** simplified to a single `uses:` call to
`PowerShellOrg/.github/.github/workflows/powershell-ci.yml@main` —
covers PS 5.1 and 7.x on Windows/Linux/macOS, installs deps, and runs
Init/Test/Analyze via `Invoke-psake`
- **publish.yml** added — triggers on `v*` tag push, delegates to
`powershell-release.yml@main` (Init → Test → Analyze → Build → Publish →
GitHub Release); requires `PSGALLERY_API_KEY` secret set in repo
settings
- **psakeFile.ps1** — added `Analyze` task (runs `Invoke-ScriptAnalyzer`
on staged output, fails on Error severity); wired
`$PSBPreference.Publish.ApiKey` from `$env:PSGALLERY_API_KEY`

## Test plan

- [x] CI run on this PR validates Init/Test/Analyze pass across all
matrix legs
- [x] Confirm `PSGALLERY_API_KEY` secret is set in repo settings before
tagging a release
- [ ] Dry-run publish by triggering `publish.yml` via
`workflow_dispatch` on a pre-release branch

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>