Releases: umn-microsoft-automation/AzureDevOpsTemplates
Releases · umn-microsoft-automation/AzureDevOpsTemplates
v2022.04.25
What's Changed
- Add Linux deploy targets by @FISHMANPET in #35
- Use python directly instead of container by @FISHMANPET in #37
Full Changelog: v2022.03.16...v2022.04.25
v2022.03.16
What's Changed
- Force turn on TLS1.2 when creating GitHub release by @FISHMANPET in #33
Full Changelog: v2022.02.04...v2022.03.16
v2021.12.17
v2021.12.17
Adds mkdocs-mermaid2-plugin to template, allowing usage of mermaid diagrams in your documentation #30 - Thanks @jbolduan!
v2021.12.03
Changes to continue functionality with 5.0 release of Install-RequiredModule
v2021.09.08
- Use Import-PowerShellDataFile instead of Test-ModuleManifest to query module version, because Test-ModuleManifest will fail if dependencies aren't installed, even though they aren't needed at this stage.
v2021.06.29
- Fixes #13 by removing the need for the deploy key entirely. Now the template will pull credentials directly from the service connection used to checkout the code when publishing a release against GitHub. The variable is left in the template for backwards compatibility, but it's no longer used.
- Removes some of the debug comments for modules, per #6 when not in debug mode.
- Rearranged the order of steps in the Publish, so the GitHub release is created before the module is published
- Synced changes from deploy-module template to deploy-module-publish-only template
v2021.04.23
v2021.01.28
The default branch for this repository has been renamed to main, and along with that #14 has been resolved. PS Modules can now use the DefaultBranch variable to specify the default branch. This will default to master for backwards compatiblity.
v2021.01.20
Adds support for mkdocs-markdownextradata-plugin to the docs template. It is now available in the pipeline and can be added to your mkdocs.yml.