Skip to content

Commit 29e2329

Browse files
Trigger the self-test publish path from the Fix label
The publish job was skipped in every self-test run, so the Settings to action input to environment variable hop was never exercised in CI. That is the hop this pull request repairs. Adding 'Fix' to the Default fixture's PrereleaseLabels resolves ReleaseType to Prerelease for the framework's own bugfix pull requests, so Publish-PSModule runs under WhatIf and logs the tag it would create. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
1 parent 06b4714 commit 29e2329

1 file changed

Lines changed: 15 additions & 0 deletions

File tree

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,18 @@
11
Name: PSModuleTest2
22
Linter:
33
Skip: true
4+
Publish:
5+
Module:
6+
# 'Fix' is here so that Process-PSModule's own self-test exercises the publish path. The framework
7+
# repository labels its bugfix pull requests 'Fix', which makes Get-PSModuleSettings resolve
8+
# ReleaseType to 'Prerelease' for this fixture, so Publish-PSModule actually runs and its resolved
9+
# release tag is visible in the workflow log. Publish-Module.yml sets WhatIf whenever the workflow
10+
# runs in PSModule/Process-PSModule, so nothing is published and no release is created.
11+
#
12+
# Never add a label that PSModule/Auto-Release recognises. It matches the literal string 'prerelease'
13+
# with -Contains, which is case-insensitive in PowerShell, and would make this repository create a
14+
# real prerelease release and tag of itself.
15+
#
16+
# This is a stopgap that covers the Settings -> action input -> environment variable hop until the
17+
# end-to-end publish harness in PSModule/Process-PSModule#436 exists.
18+
PrereleaseLabels: 'prerelease, Fix'

0 commit comments

Comments
 (0)