René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Feature]: Add ReleaseType input to Publish-PSModule for explicit release control","articleBody":"## Summary\n\nAdd a new `ReleaseType` input parameter to `Publish-PSModule` action that allows users to explicitly specify the type of release to create, overriding the automatic detection based on PR state and labels.\n\n## Motivation\n\nCurrently, the release type is automatically determined based on:\n- Whether the PR is merged\n- Whether the target is the default branch\n- Whether the PR has a `prerelease` label\n\nThere are scenarios where users need more control over the release process, such as:\n- Forcing a specific release type in CI/CD pipelines\n- Testing release workflows without relying on label-based detection\n- Integration with other tools that determine release type externally (e.g., `Get-PSModuleSettings`)\n\n## Proposed Solution\n\nAdd a `ReleaseType` input with the following valid values:\n- `Release` - Create a stable release\n- `Prerelease` - Create a prerelease\n- `Cleanup` - Delete old prereleases\n- `None` - Do not create any release\n\nWhen set, this input overrides the automatic detection logic.\n\n## Implementation\n\nThis change affects `PSModule/Publish-PSModule`:\n- Add `ReleaseType` input to `action.yml`\n- Pass environment variable to PowerShell script\n- Update release type calculation to use the input when provided\n- Simplify the event information logging (remove redundant PR state checks)\n\n## Related\n\n- Part of the broader release notes configuration work in #263","author":{"url":"https://github.com/MariusStorhaug","@type":"Person","name":"MariusStorhaug"},"datePublished":"2026-01-18T00:39:45.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/265/Process-PSModule/issues/265"}