| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
* Update script to consume .NET 7 builds
* Update target framework
* Add dotnet metadata override value
* Update dependencies
* Update analyzer
* Conditionally add output argument
* Update files.wxs
* Fix tests
* Update Microsoft.PowerShell.Native to 7.3.0-preview.1
* Disable psget tests
* Update to latest build for .NET 7 preview 1
* Disable ready to run
* Update version of `Microsoft.AspNetCore.Mvc.NewtonsoftJson` package
* Update cgmanifest and startup test
|
|
`R2R` images (#16297)
* Clean up crossgen related build scripts
* Fix ci.psm1
* Clean up '-CrossGen' use in a few other files
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Add StyleCop.Analyzers with all rules disabled
* Downgrade to 1.2.0-beta.205
* Enable SA1518: Use line endings correctly at end of file
https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1518.md
|
|
* Enable EnforceCodeStyleInBuild
* Disable rules breaking build
|
|
|
|
|
|
|
|
|
|
|
|
# PR Summary
<!-- Summarize your PR between here and the checklist. -->
## PR Context
follow-up #12190
## PR Checklist
- [x] [PR has a meaningful title](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
- Use the present tense and imperative mood when describing your changes
- [x] [Summarized changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
- [ ] [Make sure all `.h`, `.cpp`, `.cs`, `.ps1` and `.psm1` files have the correct copyright header](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
- [x] This PR is ready to merge and is not [Work in Progress](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---work-in-progress).
- If the PR is work in progress, please add the prefix `WIP:` or `[ WIP ]` to the beginning of the title (the `WIP` bot will keep its status check at `Pending` while the prefix is present) and remove the prefix when the PR is ready.
- **[Breaking changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#making-breaking-changes)**
- [x] None
- **OR**
- [ ] [Experimental feature(s) needed](https://github.com/MicrosoftDocs/PowerShell-Docs/blob/staging/reference/6/Microsoft.PowerShell.Core/About/about_Experimental_Features.md)
- [ ] Experimental feature name(s): <!-- Experimental feature name(s) here -->
- **User-facing changes**
- [x] Not Applicable
- **OR**
- [ ] [Documentation needed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
- [ ] Issue filed: <!-- Number/link of that issue here -->
- **Testing - New and feature**
- [x] N/A or can only be tested interactively
- **OR**
- [ ] [Make sure you've added a new test if existing tests do not effectively test the code changed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#before-submitting)
- **Tooling**
- [x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
- **OR**
- [ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:
- Impact on [PowerShell Editor Services](https://github.com/PowerShell/PowerShellEditorServices) which is used in the [PowerShell extension](https://github.com/PowerShell/vscode-powershell) for VSCode (which runs in a different PS Host).
- Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
- Impact on [PSScriptAnalyzer](https://github.com/PowerShell/PSScriptAnalyzer) (which provides linting & formatting in the editor extensions).
- Impact on [EditorSyntax](https://github.com/PowerShell/EditorSyntax) (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
|
|
Co-Authored-By: Nick Guerrera <nicholg@microsoft.com>
|
|
|
|
Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>
|
|
|
|
|
|
|
|
|
|
`-CrossGen` won`t work, but this gives basic ability to build for another platform.
This also means you cannot really package for another platform.
|
|
|
|
Addresses CVE-2019-0657
|
|
Bump SDK and Runtime Versions
- Also, fix alpine docker file
- Also, fix extra files being added to some Modules after these changes
|
|
|
|
|
|
* Move to .Net Core SDK 2.1.401 and runtime 2.1.3
* Update package references
|
|
* update to latest package references
* update runtime framework
* update sdk
* automatically read NuGet package dependency info from csproj, where version info is fully qualified
* update file.wxs
|
|
|
|
The main purpose of this was to enable full symbols for windows release build.
Also makes explicit where we are optimizing and where we are not optimizing due to https://github.com/dotnet/corefx/issues/29700
|
|
* Build Update
- Change `TargetFramework` to `netcoreapp2.1` and removed unnecessary `RuntimeFrameworkVersion` from `PowerShell.Common.props`
- Update dotnet SDK to 2.1.300-rc1-008662
- Update `TypeGen` target in `Build.psm1` to work with 2.1
- Rename macOS runtime to `osx-x64` as the old build logic expects 10.12 and breaks running on 10.13 system.
- Remove `PackageReference` to `System.Memory` as it's part of dotnetcore 2.1
- Update search for `crossgen` executable to find the matching version
* Test Update
- Update test tools `WebListener` to latest `asp.net core`
- Marked `AuthHeader Redirect` tests as `Pending` due to change in CoreFX
|
|
Address #6547
We begin using C# 7.2 features (Span) but .Net Core doesn't seem use "Latest" as default for a language.
So we explicitly set the value.
|
|
Update to DotNet 2.0.6
- this addresses [Microsoft Security Advisory CVE-2018-0875: Hash Collision can cause Denial of Service](https://github.com/PowerShell/Announcements/issues/4)
- This is a port of https://github.com/PowerShell/PowerShell/commit/d607f207b9726f1c8b3a115803db2c4d129127e1 to 6.1
|
|
|
|
|
|
Specify that the images (pwsh.dll in particular) support high-entropy 64-bit address space layout randomization (ASLR).
|
|
|
|
assembly (#4863)
|
|
Extract information about the release tag, number of commits since the tag and the hash of the latest commit within a MSBuild target, and bake that information into version properties of the assemblies appropriately.
|
|
* Migrate to official .NET Core 2.0
* [Feature] Remove chmod code as the issue has been fixed in dotnet
|
|
`2.0.0-preview2-006502` (#4144)
|
|
'PowerShell.Common.props' (#4106)
`AssemblyVersion` and `FileVersion` are now inferred from the `Version` property, which is inferred by `VersionPrefix`. So now both `AssemblyVersion` and `FileVersion` are 6.0.0.0 for each of PowerShell assemblies, and the `ProductVersion` and `InformationalVersion` are 6.0.0.
|
