v0.4.13

🧪 Validate Process-PSModule publish fix (PSModule/Process-PSModule#529) (#63)

Validates the publish fix in PSModule/Process-PSModule#529 end to end, against a real publication.

Why

This repository reproduced the defect in PSModule/Process-PSModule#528: merging #62 to main failed at Publish-Module before any upload was attempted.

Failing run: 33596331743 → Publish-Module job

| Package with name 'MariusTestModule', version '0.4.13' could not be
| found in repository 'PSGallery'.
##[error]Process completed with exit code 1.

The existence probe in publish.ps1 treated an absent version as fatal, so every first-time publication of a new version failed.

What this changes

File	Change
.github/workflows/Process-PSModule.yml	caller ref @v8 → @copilot/fix-publish-module-error
src/functions/public/DateAndTime/Get-CurrentDateTime.ps1	documentation only — clarifies culture behaviour of the format presets

The source change exists only to give the pipeline something to release. It is comment-only: no executable code is touched.

Pointing the caller's uses: ref at the branch is sufficient, because the reusable workflow checks out its own actions at the resolved workflow commit rather than a floating tag:

- name: Checkout Process-PSModule
  uses: actions/checkout@...
  with:
    repository: ${{ job.workflow_repository }}
    ref: ${{ job.workflow_sha }}
    path: _wf

So _wf/.github/actions/Publish-PSModule/src/publish.ps1 resolves to the fixed file, with no vendoring or pinning workarounds.

Success criteria

Stage	Expected
Plan	resolves the next version
Publish-Module (this PR)	prerelease publishes to the Gallery
Publish-Module (on merge)	stable version publishes, no PackageNotFound failure
GitHub release	created for the new version

The decisive signal is the merge publication: the probe must report "not found" without failing the job, then hand off to Publish-PSResource.

The starting point is clean — the failed run left the Gallery at 0.4.12 with no 0.4.13 release — so this is a direct before/after on the same version that previously failed.

Do not merge as-is

⚠️ The caller ref points at a branch, not a release tag. Once #529 merges and a v8 tag includes it, this must be reverted to @v8. Merging this ref permanently would pin the module to a feature branch.