PowerShell / PowerShell/PSResourceGet
Release full version to allow correct module install directories
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Summary of the new feature / enhancement
#1974 is quite a serious bug in some scenarios (caused me issues trying to deploy a downstream project, Microsoft365DSC).
Now the bug seems to be squashed (having tested the preview build) could it be released to production please?
Proposed technical implementation details (optional)
Do a new non-preview release of the module.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #1974 and the tested preview build, then inspect the repository's documented release process for publishing a non-preview module version. Done means a production release is published and the module installs into the correct directories in the reported downstream scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100