I and I suspect others, like to keep ReleaseNotes.txt in a file in the root of our GitHub repo. Burying the release notes in a PSD1 file in some dir is not a great approach from an OSS pov. Also, we don't want to duplicate this information. So when I publish my module, I grab the contents of the ReleaseNotes.txt file in the root of my repo and pass those to the -ReleaseNotes parameter. That should work just fine.
Current Behavior
I get an annoying warning about sticking the release notes in my PSD1 file which I don't really want to do for the reasons listed above. In fact, I don't think a PSD1 file is the right place for release notes.
Possible Solution
Remove the warning but allow folks to put release notes in their PSD1 if that's what they want to do.
Expected Behavior
I and I suspect others, like to keep ReleaseNotes.txt in a file in the root of our GitHub repo. Burying the release notes in a PSD1 file in some dir is not a great approach from an OSS pov. Also, we don't want to duplicate this information. So when I publish my module, I grab the contents of the ReleaseNotes.txt file in the root of my repo and pass those to the
-ReleaseNotes
parameter. That should work just fine.Current Behavior
I get an annoying warning about sticking the release notes in my PSD1 file which I don't really want to do for the reasons listed above. In fact, I don't think a PSD1 file is the right place for release notes.
Possible Solution
Remove the warning but allow folks to put release notes in their PSD1 if that's what they want to do.
Steps to Reproduce (for bugs)
Context
Your Environment