[pull] develop from chocolatey:develop #73
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
* release/0.19.0: (#882) Make use of OSS Export Command (#883 #884) Add package parameters for features (#884) Add feature toggle for Update All button (#884) Add feature toggle for This PC source (#881) Add IsUpgradeAllCommandAllowed to interface (#882) Use latest chocolatey.lib nuget package (#869) Update to use latest version of log4net (#882) Bump chocolatey dependency
This was causing a problem when attempting to publish the package to community.chocolatey.org.
* release/0.20.0: (76 commits) (#841) Add assembly to correct nuget folder (#533) Handle null culture (maint) Fix formatting (#533) Allowing setting language during install (#545) Remove NumberOfPackageVersionsForSelection (#911) Add missing disabling of install buttons (#545) Add missing tooltip on disabled install button (maint) Cleanup trailing spaces and xmlns statements (maint) Remove unused using statements (#545) Disable certain values when other features is toggled (#533) Set current culture for WPF elements (#533) Fix remote sources being reloaded on language change (#545) Mark dialog as being open when child window is opened/closed (#545) Make version editable on advanced install (#545) Add future support for log file argument (maint) Remove format support for install configuration description (#545) Add missing entry for cache location (maint) Add missing description of UseLanguage config (#770) Hide button for displaying arguments (#770) Show additional message on no arguments ...
This step, to run the botstrap of Cake modules, is actually handled in the build.ps1 directly, so isn't needed here.
This will ultimately replace the AppVeyor build that we are currently using.
At the minute, Chocolatey.Cake.Recipe doesn't run under the Cake .NET Global Tool, so let's just use the bootstrapper directly.
This includes a fix for not running Transifex when the token hasn't been configured.
Building of Chocolatey GUI hasn't been tested on anything other than Visual Studio 2019, so let's stick with that for just now. That is the version of Visual Studio installed on the windows-2019 image.
This build has been moved onto GitHub Actions instead.
Limit the execution of the action to only GitFlow branches. Cache the NuGet Packages folder between runs.
(maint) Fix typo in dialogue seen after config export is successful
*Total -- 252.41kb -> 198.68kb (21.29%) /Source/ChocolateyGui/[email protected] -- 9.64kb -> 4.76kb (50.69%) /Source/ChocolateyGui/chocolatey_logo.png -- 37.52kb -> 25.51kb (31.99%) /Source/ChocolateyGui/chocolatey.png -- 41.82kb -> 31.94kb (23.62%) /Source/ChocolateyGui/[email protected] -- 65.12kb -> 53.04kb (18.55%) /Source/ChocolateyGui/[email protected] -- 81.05kb -> 66.66kb (17.77%) /Source/ChocolateyGui/[email protected] -- 17.25kb -> 16.77kb (2.78%) Signed-off-by: ImgBotApp <[email protected]>
[ImgBot] Optimize images
In this scenario, ideally, the separator should be completely ignored.
(#915) Fix keyboard bindings in conjunction with aggregated source view
This commit adds a build definition to be used by the Chocolatey internal TeamCity server. This calls the build.official.bat script, as it will have access to the required files in order to create an official signed version of Chocolatey GUI. Setup of this build uses the build of Chocolatey GUI Licensed Extension as a template, and then modified the necessary portions to make it specific to Chocolatey GUI.
(build) Adds TeamCity build definition
Also removes unrequired imports that _aren't_ being used here.
(build) Adds Missing Dependency to Kotlin Build Definition
To make them consistent with other projects.
This includes some bug fixes for making correct use of the asserted PackageVersion, both for writing back to TeamCity, as well as when creating NuGet packages via dotnet pack.
When tagging the pullRequest build feature to a specific VCS Root, you
specify it against vcsRootExtId.
But when you want to dynamically select it, or more likely pick "the
only VCS Root configured for the project", this option is omitted
rather than trying to reference ${DslContext.settingsRoot}.
This includes a fix for ensuring that the signing steps are run when running on TeamCity. Currently they are being skipped when they shouldn't.
This includes a fix for signing on TeamCity, when the password doesn't exist on disk.
Which includes registering additional location for signtool.exe, so that it can found when running on TeamCity.
This is to ensure that the same signtool is being used on all builds, where signtool is being installed via the windows SDK (we think). At some point, we should look to getting signtool from somewhere else, so that we don't need this monster download and install.
This contains a fix to ensure that the Certificate Subject Name property is quoted, so that it is passed to the PowerShell script correctly.
(build) Install dotnet-6.0-runtime for QA Build
(#967) Parse Info messages for errors
While not "required" for this repository, updating all usages of the Recipe package to the latest version, now that a build issue has been addressed with the Chocolatey GUI Licensed Extension build.
This includes a fix specifically for when building Web Application projects, which although doesn't apply to this repository, it makes sense to update to the latest version.
If the directory for a LiteDatabase doesn't exist, LiteDatabase will not attempt to create it, and will throw an exception because it can't create the file without the parent directory. This ensures that the folder exists before trying to create the database.
(#996) Create config directory if it doesn't exist
Also change gitHubTokenVariable to gitReleaseManagerTokenVariable to reflect change in chocolatey.cake.recipe.
…ager/.templates/'
(maint) synced file(s) with chocolatey/.github
The build is failing on the hotfix branch, when it isn't on the develop branch, and this is the only immediate difference between the two branches.
No new features in this release which are applicable to Chocolatey CLI, but still good to keep this package up to date when it changes.
* hotfix/2.1.1: (build) Switch to a PowerShell step (maint) synced local '.templates/' with remote '.github/GitReleaseManager/.templates/' (build) Bump Recipe package to latest version (maint) Remove unnecessary whitespace (#996) Create config directory if it doesn't exist (maint) Remove unused pragmas (#967) Parse Info for Error, Warn, and Fatal
* master: (build) Switch to a PowerShell step (maint) synced local '.templates/' with remote '.github/GitReleaseManager/.templates/' (build) Bump Recipe package to latest version (maint) Remove unnecessary whitespace (#996) Create config directory if it doesn't exist (maint) Remove unused pragmas (#967) Parse Info for Error, Warn, and Fatal (maint) Remove mention of services no longer used (tests) Update Pester tests to be consistent (tests) Move the Pester tests to be consistent (maint) synced local '.templates/' with remote '.github/GitReleaseManager/.templates/' (maint) Update GRM configuration
Based on changes to how the Authenticode signing works (namely the need to use a hardware HSM, or a software as a service based solution), we need to look to prevent unnecessary signing of files happening. Signing of files is not required on the scheduled Integration Testing and SonarQube builds, so we are removing it from these builds. This is done using the command line options for: --shouldAuthenticodeSignMsis=false --shouldAuthenticodeSignOutputAssemblies=false --shouldAuthenticodeSignPowerShellScripts=false
(build) (ENGTASKS-3694) Update Chocolatey.Cake.Recipe to latest
In the previous round of changes, we were a little too quick to remove the signing step from the main build configuration. This is needed, as well as calling build.official.bat, in order to get an official release. The other build configurations, except the signing scripts, one, don't need the signing keys in place, so this has also been done in this commit.
This commit takes the newly signed PowerShell scripts from the build server and adds them into the source code repository. A new process for re-signing the files will be followed to ensure that the signature remains in tact.
…hub/workflows/stale.yml'
(maint) synced file(s) with chocolatey/.github
This is an attempt to ensure that any changes to our dependencies, whether that is: * changes to NuGet packages through packages.config files Are tracked and updated properly. By making these files/folder owned by the new @chocolatey-credits-reviewers group, it means that a member of that group will be flagged on any PR's that we raised that contain these files.
This extension is useful when editing Markdown files, especially when it contains a Table Of Contents. This extension will update the TOC simply by making changes to the main body.
(maint) Add recommended extension
v2 of the upload-artifact action is now deprecated, and the recommendation is to move to using v4: https://github.blog/changelog/2024-02-13-deprecation-notice-v1-and-v2-of-the-artifact-actions/
(build) Add templated notifications to all build configurations
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )