Skip to content

⚙️ [Maintenance]: Workflow actions follow the selected revision#385

Draft
Marius Storhaug (MariusStorhaug) wants to merge 4 commits into
mainfrom
feat/internalize-process-actions
Draft

⚙️ [Maintenance]: Workflow actions follow the selected revision#385
Marius Storhaug (MariusStorhaug) wants to merge 4 commits into
mainfrom
feat/internalize-process-actions

Conversation

@MariusStorhaug

@MariusStorhaug Marius Storhaug (MariusStorhaug) commented Jul 15, 2026

Copy link
Copy Markdown
Member

Process-PSModule now carries the actions used only by its pipeline. Consumers continue to call one reusable workflow, while the workflow and its action set execute from the same selected revision for both released tags and in-progress development branches.

Changed: Action versions follow the selected workflow

A consumer keeps its existing reusable-workflow reference. When it selects a release tag, the matching released action set runs; when the workflow is exercised from a development branch, that branch's action changes run together with it. No caller inputs or action references are required.

Technical Details

  • Nine Process-PSModule-only actions now live under .github/actions/ with their manifests and source code.
  • Twelve stage workflows self-check out the invoked Process-PSModule revision into _wf; thirteen action call sites resolve from that checkout.
  • Nested action dependencies on Install-PSModuleHelpers now resolve from the same bundled revision.
  • DEPENDENCIES.md distinguishes bundled actions from the three remaining external PSModule action dependencies.
  • Action READMEs and test-suite consolidation are intentionally out of scope for this change.
  • Implementation plan progress: Step 1.1 (internal action packages) and Step 1.3 (workflow self-checkout and local resolution) are complete; Step 1.2 is intentionally excluded.

Validation

No issue is linked; this PR proceeds by explicit maintainer direction.

PSMODULE_BUILD_PSMODULE_INPUT_Prerelease: ${{ inputs.Prerelease }}
run: |
# Build-PSModule
${{ github.action_path }}/src/main.ps1
working-directory: ${{ inputs.WorkingDirectory }}
run: |
# Build-PSModuleDocumentation
${{ github.action_path }}/src/main.ps1
shell: pwsh
run: |
# Install-PSModuleHelpers
${{ github.action_path }}/src/main.ps1
PSMODULE_PUBLISH_PSMODULE_INPUT_UsePRBodyAsReleaseNotes: ${{ inputs.UsePRBodyAsReleaseNotes }}
PSMODULE_PUBLISH_PSMODULE_INPUT_UsePRTitleAsReleaseName: ${{ inputs.UsePRTitleAsReleaseName }}
PSMODULE_PUBLISH_PSMODULE_INPUT_UsePRTitleAsNotesHeading: ${{ inputs.UsePRTitleAsNotesHeading }}
run: ${{ github.action_path }}/src/publish.ps1
env:
PSMODULE_PUBLISH_PSMODULE_INPUT_WhatIf: ${{ inputs.WhatIf }}
PSMODULE_PUBLISH_PSMODULE_CONTEXT_ReleaseTag: ${{ env.PSMODULE_PUBLISH_PSMODULE_CONTEXT_ReleaseTag }}
run: ${{ github.action_path }}/src/cleanup.ps1
PSMODULE_TEST_PSMODULE_INPUT_Settings: ${{ inputs.Settings }}
run: |
# Get test paths
${{ github.action_path }}/src/main.ps1
@github-actions

github-actions Bot commented Jul 15, 2026

Copy link
Copy Markdown

Super-linter summary

Language Validation result
CHECKOV Pass ✅
GITLEAKS Pass ✅
GIT_MERGE_CONFLICT_MARKERS Pass ✅
MARKDOWN Pass ✅
NATURAL_LANGUAGE Pass ✅
POWERSHELL Pass ✅
PRE_COMMIT Pass ✅
SPELL_CODESPELL Pass ✅
TRIVY Pass ✅
YAML Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter

@MariusStorhaug Marius Storhaug (MariusStorhaug) changed the title feat: internalize Process-PSModule actions ⚙️ [Maintenance]: Workflow actions follow the selected revision Jul 15, 2026
@MariusStorhaug Marius Storhaug (MariusStorhaug) marked this pull request as draft July 15, 2026 01:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants